You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(7) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(9) |
Feb
(4) |
Mar
(20) |
Apr
(10) |
May
(5) |
Jun
(2) |
Jul
(10) |
Aug
(4) |
Sep
(15) |
Oct
(5) |
Nov
(8) |
Dec
(2) |
| 2003 |
Jan
(11) |
Feb
(5) |
Mar
(10) |
Apr
(20) |
May
(24) |
Jun
(13) |
Jul
(6) |
Aug
(5) |
Sep
(10) |
Oct
(10) |
Nov
(9) |
Dec
(7) |
| 2004 |
Jan
(4) |
Feb
(10) |
Mar
(5) |
Apr
(18) |
May
(18) |
Jun
(14) |
Jul
(24) |
Aug
(14) |
Sep
(6) |
Oct
(18) |
Nov
(5) |
Dec
(3) |
| 2005 |
Jan
(5) |
Feb
(1) |
Mar
(5) |
Apr
(10) |
May
(10) |
Jun
(16) |
Jul
(46) |
Aug
(36) |
Sep
(16) |
Oct
(11) |
Nov
(12) |
Dec
(29) |
| 2006 |
Jan
(33) |
Feb
(45) |
Mar
(42) |
Apr
(23) |
May
(23) |
Jun
(21) |
Jul
(19) |
Aug
(23) |
Sep
(17) |
Oct
(50) |
Nov
(74) |
Dec
(44) |
| 2007 |
Jan
(35) |
Feb
(18) |
Mar
(46) |
Apr
(25) |
May
(26) |
Jun
(24) |
Jul
(33) |
Aug
(4) |
Sep
(41) |
Oct
(43) |
Nov
(23) |
Dec
(42) |
| 2008 |
Jan
(26) |
Feb
(20) |
Mar
(21) |
Apr
(18) |
May
(28) |
Jun
(32) |
Jul
(25) |
Aug
(28) |
Sep
(27) |
Oct
(34) |
Nov
(16) |
Dec
(42) |
| 2009 |
Jan
(21) |
Feb
(36) |
Mar
(40) |
Apr
(51) |
May
(27) |
Jun
(13) |
Jul
(38) |
Aug
(40) |
Sep
(5) |
Oct
(14) |
Nov
(4) |
Dec
(7) |
| 2010 |
Jan
(16) |
Feb
(10) |
Mar
(38) |
Apr
(83) |
May
(27) |
Jun
(41) |
Jul
(57) |
Aug
(24) |
Sep
(14) |
Oct
(22) |
Nov
(28) |
Dec
(42) |
| 2011 |
Jan
(52) |
Feb
(13) |
Mar
(41) |
Apr
(14) |
May
(24) |
Jun
(14) |
Jul
(16) |
Aug
(15) |
Sep
(19) |
Oct
(20) |
Nov
(35) |
Dec
(48) |
| 2012 |
Jan
(30) |
Feb
(9) |
Mar
(33) |
Apr
(15) |
May
(13) |
Jun
(13) |
Jul
(57) |
Aug
(20) |
Sep
(18) |
Oct
(29) |
Nov
(28) |
Dec
(9) |
| 2013 |
Jan
(19) |
Feb
(26) |
Mar
(44) |
Apr
(13) |
May
(38) |
Jun
(6) |
Jul
(24) |
Aug
(8) |
Sep
(7) |
Oct
(10) |
Nov
(12) |
Dec
(6) |
| 2014 |
Jan
(13) |
Feb
(6) |
Mar
(41) |
Apr
(5) |
May
(4) |
Jun
(3) |
Jul
(13) |
Aug
(9) |
Sep
(35) |
Oct
(36) |
Nov
(16) |
Dec
(4) |
| 2015 |
Jan
(6) |
Feb
(4) |
Mar
(7) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(2) |
Sep
(10) |
Oct
(4) |
Nov
(13) |
Dec
(3) |
| 2016 |
Jan
(6) |
Feb
(12) |
Mar
(6) |
Apr
(21) |
May
(9) |
Jun
(16) |
Jul
(13) |
Aug
(13) |
Sep
(11) |
Oct
(9) |
Nov
(20) |
Dec
(18) |
| 2017 |
Jan
(7) |
Feb
(19) |
Mar
(9) |
Apr
(12) |
May
(12) |
Jun
(35) |
Jul
(7) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
(4) |
Dec
|
| 2018 |
Jan
(4) |
Feb
(1) |
Mar
(3) |
Apr
(8) |
May
(9) |
Jun
(8) |
Jul
(6) |
Aug
(7) |
Sep
(8) |
Oct
(1) |
Nov
(6) |
Dec
|
| 2019 |
Jan
(6) |
Feb
(9) |
Mar
(3) |
Apr
(3) |
May
(4) |
Jun
|
Jul
|
Aug
(4) |
Sep
(3) |
Oct
(3) |
Nov
(3) |
Dec
(1) |
| 2020 |
Jan
(4) |
Feb
(4) |
Mar
(22) |
Apr
(1) |
May
(16) |
Jun
(12) |
Jul
(3) |
Aug
(10) |
Sep
(5) |
Oct
(1) |
Nov
(24) |
Dec
(1) |
| 2021 |
Jan
(2) |
Feb
(10) |
Mar
(9) |
Apr
(7) |
May
(8) |
Jun
(10) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2022 |
Jan
(3) |
Feb
(4) |
Mar
(5) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
(6) |
Sep
(1) |
Oct
(2) |
Nov
(2) |
Dec
|
| 2023 |
Jan
(2) |
Feb
(6) |
Mar
|
Apr
|
May
(13) |
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
(1) |
Dec
(4) |
| 2024 |
Jan
(3) |
Feb
|
Mar
(5) |
Apr
(1) |
May
(5) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(3) |
Nov
(3) |
Dec
|
| 2025 |
Jan
|
Feb
(5) |
Mar
(33) |
Apr
(8) |
May
(10) |
Jun
(7) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Johan I. <joh...@is...> - 2017-08-29 11:39:38
|
Dear All, I want to create a plugin for replication purposes between Oracle to Oracle, MsSQL to MsSQL, and DB2 to Oracle. Would you kindly guide me as to which documentation links I should read on first to implement the plugins? But if there already exist such plugin would you kindly point me to it. Thank you so much. Best Regards, Johan |
|
From: Vitek C. <vit...@gm...> - 2017-08-04 11:12:51
|
Hello fellow developers, I am running the latest daily build on linux with substance L&F. I am looking for a way to get rid of shining white background of the main SQL editor pane (RSyntaxTextArea)? Is there a way to influence it? There are quire a few coloring options scattered around the menus however none seems to have any effect on it. Cheers Vitek |
|
From: Alex M. <ale...@bl...> - 2017-08-03 17:11:32
|
Currently I am working with the 9.6 server under FreeBSD 11.1 via the 42.1.4 JDBC driver. When I look at the tables and views under information_schema schema through the Squirrel Content tab, all values of all columns in all of those tables and views without exception come across as <UnknownType (2,001)>. Is this expected, or is anything wrong in my configuration? All driver and alias properties are the default values. This is the connection string just in case: jdbc:postgresql://10.1.1.144:5432/testdb Thank you! Alex [cid:image001.png@01D30C5A.01780870] [cid:image002.png@01D30C5A.01780870] [cid:image003.png@01D30C5A.01780870] |
|
From: Federico B. <fe...@in...> - 2017-07-28 17:21:41
|
Well, it turns out that what causes the hanging is the "Run all SQLs in editor" button. The same SQL which fails using Alt+Shift+Enter works fine if I select it and type Ctrl+Enter. My query contains two statements: SET SCHEMA MYSCHEMA; SELECT SOMETHING FROM WHATEVER; I tried reproducing the error using minimal examples, but everything works fine. I'll use Ctrl+Enter to avoid the problem. Il giorno ven 30 giu 2017 alle 18:47, Cosmin Blaga <dre...@gm...> ha scritto: > The error you posted indicates that something went wrong with the > look and feel of Squirrel. I doubt it has anything to do with your > pb, but try setting the default L&F and see if the error appears > again. > > For the query you might try different things. Like refining the > filter on it, trying to bring less columns in it. Eliminate parts of > it until you see what causes the blockage. Divide et impera. You can > also try an analysis on it to see what generates more load (if it's > Oracle) > > > On 30 Jun 2017 14:58, "Federico Bruni" <fe...@in...> wrote: >> Hi all >> >> I've launched a query that used to work in the past (I track my >> query scripts in a git repository and I commit them only after >> testing them) and now causes Squirrel to hang forever until I end >> the process using kill. >> >> How can I debug it? >> I've looked in the log file but cannot see anything suspicious. >> >> Thanks in advance for any pointer >> Federico >> >> PS I found this error in the log. No idea if it's related to the >> hanging: >> >> >> 2017-06-30 13:20:05,246 [AWT-EventQueue-1] ERROR >> net.sourceforge.squirrel_sql.plugins.laf.jtattoo.JTattooLafData - >> Unable to load LAF class >> (com.jtattoo.plaf.mint.MintLookAndFeel):com.jtattoo.plaf.mint.MintLookAndFeel >> java.lang.ClassNotFoundException: >> com.jtattoo.plaf.mint.MintLookAndFeel >> at java.net.URLClassLoader.findClass(URLClassLoader.java:381) >> at >> net.sourceforge.squirrel_sql.fw.util.MyURLClassLoader.findClass(MyURLClassLoader.java:209) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:424) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:357) >> at java.lang.Class.forName0(Native Method) >> at java.lang.Class.forName(Class.java:348) >> at >> net.sourceforge.squirrel_sql.plugins.laf.jtattoo.JTattooLafData.putClass(JTattooLafData.java:82) >> at >> net.sourceforge.squirrel_sql.plugins.laf.jtattoo.JTattooLafData.initLafMap(JTattooLafData.java:62) >> at >> net.sourceforge.squirrel_sql.plugins.laf.jtattoo.JTattooLafData.<init>(JTattooLafData.java:49) >> at >> net.sourceforge.squirrel_sql.plugins.laf.jtattoo.JTattooLookAndFeelController.<init>(JTattooLookAndFeelController.java:92) >> at >> net.sourceforge.squirrel_sql.plugins.laf.LAFRegister.installLookAndFeelControllers(LAFRegister.java:461) >> at >> net.sourceforge.squirrel_sql.plugins.laf.LAFRegister.<init>(LAFRegister.java:141) >> at >> net.sourceforge.squirrel_sql.plugins.laf.LAFPlugin.load(LAFPlugin.java:211) >> at >> net.sourceforge.squirrel_sql.client.plugin.PluginManager.loadPlugin(PluginManager.java:649) >> at >> net.sourceforge.squirrel_sql.client.plugin.PluginManager.loadPlugins(PluginManager.java:452) >> at >> net.sourceforge.squirrel_sql.client.Application.executeStartupTasks(Application.java:726) >> at >> net.sourceforge.squirrel_sql.client.Application.startup(Application.java:216) >> at net.sourceforge.squirrel_sql.client.Main$2.run(Main.java:118) >> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311) >> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756) >> at java.awt.EventQueue.access$500(EventQueue.java:97) >> at java.awt.EventQueue$3.run(EventQueue.java:709) >> at java.awt.EventQueue$3.run(EventQueue.java:703) >> at java.security.AccessController.doPrivileged(Native Method) >> at >> java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80) >> at java.awt.EventQueue.dispatchEvent(EventQueue.java:726) >> at >> net.sourceforge.squirrel_sql.client.Main$1.dispatchEvent(Main.java:99) >> at >> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201) >> at >> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) >> at >> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) >> at >> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) >> at >> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) >> at java.awt.EventDispatchThread.run(EventDispatchThread.java:82) >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Squirrel-sql-users mailing list >> Squ...@li... >> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users |
|
From: Alex M. <ale...@bl...> - 2017-07-14 15:19:38
|
And you tried using both db2jcc.jar and db2jcc4.jar? I do not recall any problems connecting, but also can't recall which JAR I have used, as it's been years since configuring and I am away from the datacenter now. Years ago when I was starting to use Squirrel with DB2 and DB/400 I used this link to set up: https://www.ibm.com/developerworks/data/library/techarticle/dm-0312bhogal/index.html Thank you Alex From: Craig Mangum [mailto:Cra...@sa...] Sent: Friday, July 14, 2017 10:20 AM To: squ...@li... Subject: [Squirrel-sql-users] Cannot Connect to DB2 I am unsuccessful trying to connect to DB2 using Squirrel SQL Client Version 3.7.1 I can connect to Greenplum, Oracle, Postgres, SQL Server and Teradata with no problems. My setup is this: Squirrel SQL Client Version 3.7.1 Java Runtime Version: 1.8.0_131-b11 OS System: Windows Server 2012 R2 64-bit Java Class Version: 52.0 DB2 Version: DB2 V10.5.0.420, Fix Pack 0 JDBC Driver Version: 4.16.53 to match DB2 V10.5 FP0 and FP1 I have tried multiple versions of JDBC and I always get the following slack trace output. This seems to be some sort of mis-match between versions of DB2 and JDBC. Does anyone know the proper JDBC jar for my setup above? java.util.concurrent.ExecutionException: java.lang.RuntimeException: com.ibm.db2.jcc.am.DisconnectNonTransientException: [jcc][t4][2034][11148][4.16.53] Execution failed due to a distribution protocol error that caused deallocation of the conversation. A DRDA Data Stream Syntax Error was detected. Reason: 0x13. ERRORCODE=-4499, SQLSTATE=58009 at java.util.concurrent.FutureTask.report(Unknown Source) at java.util.concurrent.FutureTask.get(Unknown Source) at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.awaitConnection(OpenConnectionCommand.java:132) at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.access$100(OpenConnectionCommand.java:45) at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand$2.run(OpenConnectionCommand.java:115) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.RuntimeException: com.ibm.db2.jcc.am.DisconnectNonTransientException: [jcc][t4][2034][11148][4.16.53] Execution failed due to a distribution protocol error that caused deallocation of the conversation. A DRDA Data Stream Syntax Error was detected. Reason: 0x13. ERRORCODE=-4499, SQLSTATE=58009 at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.executeConnect(OpenConnectionCommand.java:171) at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.access$000(OpenConnectionCommand.java:45) at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand$1.run(OpenConnectionCommand.java:104) ... 5 more Caused by: com.ibm.db2.jcc.am.DisconnectNonTransientException: [jcc][t4][2034][11148][4.16.53] Execution failed due to a distribution protocol error that caused deallocation of the conversation. A DRDA Data Stream Syntax Error was detected. Reason: 0x13. ERRORCODE=-4499, SQLSTATE=58009 at com.ibm.db2.jcc.am.fd.a(fd.java:322) at com.ibm.db2.jcc.am.fd.a(fd.java:428) at com.ibm.db2.jcc.t4.x.j(x.java:998) at com.ibm.db2.jcc.t4.x.c(x.java:496) at com.ibm.db2.jcc.t4.x.v(x.java:1201) at com.ibm.db2.jcc.t4.y.d(y.java:150) at com.ibm.db2.jcc.t4.b.k(b.java:1385) at com.ibm.db2.jcc.t4.b.b(b.java:1297) at com.ibm.db2.jcc.t4.b.a(b.java:6433) at com.ibm.db2.jcc.t4.b.b(b.java:848) at com.ibm.db2.jcc.t4.b.a(b.java:765) at com.ibm.db2.jcc.t4.b.a(b.java:423) at com.ibm.db2.jcc.t4.b.a(b.java:398) at com.ibm.db2.jcc.t4.b.<init>(b.java:336) at com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(DB2SimpleDataSource.java:233) at com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(DB2SimpleDataSource.java:199) at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:474) at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:115) at net.sourceforge.squirrel_sql.fw.sql.SQLDriverManager.getConnection(SQLDriverManager.java:133) at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.executeConnect(OpenConnectionCommand.java:167) |
|
From: Craig M. <Cra...@sa...> - 2017-07-14 14:20:29
|
I am unsuccessful trying to connect to DB2 using Squirrel SQL Client Version 3.7.1 I can connect to Greenplum, Oracle, Postgres, SQL Server and Teradata with no problems.
My setup is this:
Squirrel SQL Client Version 3.7.1
Java Runtime Version: 1.8.0_131-b11
OS System: Windows Server 2012 R2 64-bit
Java Class Version: 52.0
DB2 Version: DB2 V10.5.0.420, Fix Pack 0
JDBC Driver Version: 4.16.53 to match DB2 V10.5 FP0 and FP1
I have tried multiple versions of JDBC and I always get the following slack trace output. This seems to be some sort of mis-match between versions of DB2 and JDBC. Does anyone know the proper JDBC jar for my setup above?
java.util.concurrent.ExecutionException: java.lang.RuntimeException: com.ibm.db2.jcc.am.DisconnectNonTransientException: [jcc][t4][2034][11148][4.16.53] Execution failed due to a distribution protocol error that caused deallocation of the conversation.
A DRDA Data Stream Syntax Error was detected. Reason: 0x13. ERRORCODE=-4499, SQLSTATE=58009
at java.util.concurrent.FutureTask.report(Unknown Source)
at java.util.concurrent.FutureTask.get(Unknown Source)
at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.awaitConnection(OpenConnectionCommand.java:132)
at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.access$100(OpenConnectionCommand.java:45)
at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand$2.run(OpenConnectionCommand.java:115)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: com.ibm.db2.jcc.am.DisconnectNonTransientException: [jcc][t4][2034][11148][4.16.53] Execution failed due to a distribution protocol error that caused deallocation of the conversation.
A DRDA Data Stream Syntax Error was detected. Reason: 0x13. ERRORCODE=-4499, SQLSTATE=58009
at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.executeConnect(OpenConnectionCommand.java:171)
at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.access$000(OpenConnectionCommand.java:45)
at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand$1.run(OpenConnectionCommand.java:104)
... 5 more
Caused by: com.ibm.db2.jcc.am.DisconnectNonTransientException: [jcc][t4][2034][11148][4.16.53] Execution failed due to a distribution protocol error that caused deallocation of the conversation.
A DRDA Data Stream Syntax Error was detected. Reason: 0x13. ERRORCODE=-4499, SQLSTATE=58009
at com.ibm.db2.jcc.am.fd.a(fd.java:322)
at com.ibm.db2.jcc.am.fd.a(fd.java:428)
at com.ibm.db2.jcc.t4.x.j(x.java:998)
at com.ibm.db2.jcc.t4.x.c(x.java:496)
at com.ibm.db2.jcc.t4.x.v(x.java:1201)
at com.ibm.db2.jcc.t4.y.d(y.java:150)
at com.ibm.db2.jcc.t4.b.k(b.java:1385)
at com.ibm.db2.jcc.t4.b.b(b.java:1297)
at com.ibm.db2.jcc.t4.b.a(b.java:6433)
at com.ibm.db2.jcc.t4.b.b(b.java:848)
at com.ibm.db2.jcc.t4.b.a(b.java:765)
at com.ibm.db2.jcc.t4.b.a(b.java:423)
at com.ibm.db2.jcc.t4.b.a(b.java:398)
at com.ibm.db2.jcc.t4.b.<init>(b.java:336)
at com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(DB2SimpleDataSource.java:233)
at com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(DB2SimpleDataSource.java:199)
at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:474)
at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:115)
at net.sourceforge.squirrel_sql.fw.sql.SQLDriverManager.getConnection(SQLDriverManager.java:133)
at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.executeConnect(OpenConnectionCommand.java:167)
|
|
From: Pavan K. <pav...@gm...> - 2017-07-07 08:45:20
|
Oh alright. Thanks for a speedy reply! Regards, Pavan Kumar K N |
|
From: Gerd W. <ger...@t-...> - 2017-07-06 18:55:03
|
Am 06.07.2017 um 12:36 schrieb Pavan Kumar: > Hi Guys, > > Is there a way to build queries containing subqueries in the Query Builder > Plug-in in SQuirreL? Sorry, but there isn't. Gerd |
|
From: Pavan K. <pav...@gm...> - 2017-07-06 10:37:08
|
Hi Guys, Is there a way to build queries containing subqueries in the Query Builder Plug-in in SQuirreL? Regards, Pavan Kumar K. N. |
|
From: Gerd W. <ger...@t-...> - 2017-07-03 20:27:34
|
Max, I just committed a feature that may suit your needs. Here's the change.log excerpt: The format floating point numbers can now be user defined. See menu File --> Global Preferences --> Tab 'Data Type Controls --> section 'FLOAT, REAL, ...' There will be a snapshot soon that contains the feature. Gerd Am 16.06.2017 um 09:39 schrieb Massimo Re: > Ok Gerd, but in this case i've as decimal separator point instead comma ... > > I remember that in previous version of Squirrel this particular > editation of numbers was non present. > Could be ? > > So it would be great to introduce a specific option in : > Global Preference ---> Tab "Data Type Controls" ---> Section "Float, > Real, Double, Numeric" ... > > > Let me know. > > Thank you for your support. > > Max > > > > 2017-06-15 16:12 GMT+02:00 Gerd Wagner <ger...@t-... > <mailto:ger...@t-...>>: > > Hi Max, > > how about using the standard format? It has no thousands separators > but uses '.' as fraction separator. > > If so got menu File --> Global Preferences --> Tab 'Data Type > Controls' --> Section 'FLOAT, REAL, DOUBLE, NUMERIC ... ' > > Gerd > > Am 13.06.2017 um 09:54 schrieb Massimo Re: > > Hi all > > Actually i use Squirrel 3.7.1 with Oracle ad SQLSERVER Dbase, > > Numeric fields shown in data results after SELECT * FROM are > displayed with thousand separator... > > *Example 1* > > Immagine incorporata 1 > > Is possible display fields without thousand separator ? > > In the example above first row my desidered result value is > > 20170606101639 > > *Example 2* > > 123.456,78 --> Actual > > 123456,78 ----> Desidered > > > I've tried to check in general preferences, but nothing > > Any suggestions ? > > > Thank you for your support. > > -- > Ma > x > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > Squirrel-sql-users mailing list > Squ...@li... > <mailto:Squ...@li...> > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users > <https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users> > > > > > -- > Massimo Re |
|
From: Federico B. <fe...@in...> - 2017-06-30 11:56:51
|
Hi all I've launched a query that used to work in the past (I track my query scripts in a git repository and I commit them only after testing them) and now causes Squirrel to hang forever until I end the process using kill. How can I debug it? I've looked in the log file but cannot see anything suspicious. Thanks in advance for any pointer Federico PS I found this error in the log. No idea if it's related to the hanging: 2017-06-30 13:20:05,246 [AWT-EventQueue-1] ERROR net.sourceforge.squirrel_sql.plugins.laf.jtattoo.JTattooLafData - Unable to load LAF class (com.jtattoo.plaf.mint.MintLookAndFeel):com.jtattoo.plaf.mint.MintLookAndFeel java.lang.ClassNotFoundException: com.jtattoo.plaf.mint.MintLookAndFeel at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at net.sourceforge.squirrel_sql.fw.util.MyURLClassLoader.findClass(MyURLClassLoader.java:209) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at net.sourceforge.squirrel_sql.plugins.laf.jtattoo.JTattooLafData.putClass(JTattooLafData.java:82) at net.sourceforge.squirrel_sql.plugins.laf.jtattoo.JTattooLafData.initLafMap(JTattooLafData.java:62) at net.sourceforge.squirrel_sql.plugins.laf.jtattoo.JTattooLafData.<init>(JTattooLafData.java:49) at net.sourceforge.squirrel_sql.plugins.laf.jtattoo.JTattooLookAndFeelController.<init>(JTattooLookAndFeelController.java:92) at net.sourceforge.squirrel_sql.plugins.laf.LAFRegister.installLookAndFeelControllers(LAFRegister.java:461) at net.sourceforge.squirrel_sql.plugins.laf.LAFRegister.<init>(LAFRegister.java:141) at net.sourceforge.squirrel_sql.plugins.laf.LAFPlugin.load(LAFPlugin.java:211) at net.sourceforge.squirrel_sql.client.plugin.PluginManager.loadPlugin(PluginManager.java:649) at net.sourceforge.squirrel_sql.client.plugin.PluginManager.loadPlugins(PluginManager.java:452) at net.sourceforge.squirrel_sql.client.Application.executeStartupTasks(Application.java:726) at net.sourceforge.squirrel_sql.client.Application.startup(Application.java:216) at net.sourceforge.squirrel_sql.client.Main$2.run(Main.java:118) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756) at java.awt.EventQueue.access$500(EventQueue.java:97) at java.awt.EventQueue$3.run(EventQueue.java:709) at java.awt.EventQueue$3.run(EventQueue.java:703) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80) at java.awt.EventQueue.dispatchEvent(EventQueue.java:726) at net.sourceforge.squirrel_sql.client.Main$1.dispatchEvent(Main.java:99) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93) at java.awt.EventDispatchThread.run(EventDispatchThread.java:82) |
|
From: Alex M. <ale...@bl...> - 2017-06-29 21:12:16
|
Yeah, and that is why the settings option was probably put in place: to let those who like ODBC format use it, and let the rest use MS format.
It just should apply to generated script output, that's it. But currently both highlighted seem to have no effect:
[cid:image001.png@01D2F0FA.D65F3660]
Thank you!
Alex
-----Original Message-----
From: John Hardin [mailto:jh...@im...]
Sent: Thursday, June 29, 2017 4:47 PM
To: Alex Malmyguine
Cc: squ...@li...
Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server
On Thu, 29 Jun 2017, Alex Malmyguine wrote:
> Virtually every MS SQL developer would be confused to a high degree by
> this format, as it is virtually never used anywhere in MS SQL Server
> environments. Using JDBC is a tiny niche practice whereas the hugely
> vast majority use nothing but SSMS. Insisting on forcing this format
> on them would not be welcome.
>
> The setting for specifying date/timestamp formats is already in
> Squirrel, all that you might want to do is apply it to the output of
> the generated scripts.
Counterargument: while the {ts} format is unexpected, it *does* work (assuming the decimal places are limited), and (this is the important bit) it has the benefit of being robust in the face of different locales' date formats.
If you're generating locale-specific-formatted date data in SQL, sure it will work when *you* run that SQL, but relying it to work always for everyone will eventually come back to bite you.
Yes, I've been badly bitten by this assumption in the past.
So there might need to be a separate date option for generated SQL, offering localized date formats or {ts} format with specified decimal places, or a locale-independent common format (e.g. ISO 8601).
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jh...@im...<mailto:jh...@im...> FALaholic #11174 pgpk -a jh...@im...<mailto:jh...@im...>
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
...every time I sit down in front of a Windows machine I feel as
if the computer is just a place for the manufacturers to put their
advertising. -- fwadling on Y! SCOX
-----------------------------------------------------------------------
5 days until the 241st anniversary of the Declaration of Independence
|
|
From: John H. <jh...@im...> - 2017-06-29 20:47:20
|
On Thu, 29 Jun 2017, Alex Malmyguine wrote:
> Virtually every MS SQL developer would be confused to a high degree by
> this format, as it is virtually never used anywhere in MS SQL Server
> environments. Using JDBC is a tiny niche practice whereas the hugely
> vast majority use nothing but SSMS. Insisting on forcing this format on
> them would not be welcome.
>
> The setting for specifying date/timestamp formats is already in
> Squirrel, all that you might want to do is apply it to the output of the
> generated scripts.
Counterargument: while the {ts} format is unexpected, it *does* work
(assuming the decimal places are limited), and (this is the important bit)
it has the benefit of being robust in the face of different locales' date
formats.
If you're generating locale-specific-formatted date data in SQL, sure it
will work when *you* run that SQL, but relying it to work always for
everyone will eventually come back to bite you.
Yes, I've been badly bitten by this assumption in the past.
So there might need to be a separate date option for generated SQL,
offering localized date formats or {ts} format with specified decimal
places, or a locale-independent common format (e.g. ISO 8601).
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jh...@im... FALaholic #11174 pgpk -a jh...@im...
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
...every time I sit down in front of a Windows machine I feel as
if the computer is just a place for the manufacturers to put their
advertising. -- fwadling on Y! SCOX
-----------------------------------------------------------------------
5 days until the 241st anniversary of the Declaration of Independence
|
|
From: Pavan K. <pav...@gm...> - 2017-06-29 14:01:12
|
Hi All, I am using the SQuirreL 3.7.1 and I notice that there aren't any plugins available for Teradata or Hive. I am able to add the JDBC driver for Teradata and connect to the database. But sometimes, the tool does not behave normally. For example, when I drag and drop tables into the query builder tab, the relationships between tables are not shown. Also, the database name and schema name prefixes are not added to table names when I build queries. I am assuming these issues stem from the fact that there is no plugin support for Teradata. Is anyone currently working on plugins for Teradata and/or Hive? It would be of great use. Thanks and Regards, Pavan |
|
From: Alex M. <ale...@bl...> - 2017-06-29 13:54:39
|
Virtually every MS SQL developer would be confused to a high degree by this format, as it is virtually never used anywhere in MS SQL Server environments. Using JDBC is a tiny niche practice whereas the hugely vast majority use nothing but SSMS. Insisting on forcing this format on them would not be welcome. The setting for specifying date/timestamp formats is already in Squirrel, all that you might want to do is apply it to the output of the generated scripts. Hope that clarifies the confusion. Thank you! Alex From: Neville Rowe [mailto:row...@ho...] Sent: Wednesday, June 28, 2017 5:28 PM To: Alex Malmyguine Cc: squ...@li... Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server Hi Alex, The documents Gerd linked to are the JDBC standard documents as defined by JSR-000221 under the Java Community Process. Those documents define exactly how a JDBC v4.2 driver should operate. According to Microsoft here https://docs.microsoft.com/en-us/sql/connect/jdbc/using-sql-escape-sequences the MS JDBC driver support this escape sequence. We choose to support this in Squirrel since as this is part of the JDBC standard it should work across all JDBC drivers, rather than us having to do something different per driver / database. >> Can you provide an example of a working SQL statement with that as a datetime value, executable in SQL server? When you say ‘executable in SQL server’ - this is a JDBC standard escape sequence, so it is executable in SQL Server so long as the connection to the server is over JDBC. As per the enclosed screenshot of a quick Java test program. Horses for courses - the syntax you had will work on MS SQL Server irrespective of connection type, the syntax SquirrelSQL supports should work on all JDBC connections irrespective of server type. However the problem with your example is the length of the milliseconds - this fails select {ts '2017-02-24 10:56:12.790000’} But this succeeds select {ts '2017-02-24 10:56:12.790'} As per the below screenshot. If we (SquirrelSQL) are putting the extra zero’s in when extracting the value then we’ve got a bug to fix. [cid:image001.jpg@01D2F0BD.B36F0B90] N. On 28 Jun 2017, at 21:04, Alex Malmyguine <ale...@bl...<mailto:ale...@bl...>> wrote: Can you provide an example of a working SQL statement with that as a datetime value, executable in SQL server? Thank you Alex -----Original Message----- From: Alexandre Peshansky [mailto:Ale...@ei...] Sent: Wednesday, June 28, 2017 3:50 PM To: Alex Malmyguine Cc: squ...@li...<mailto:squ...@li...> Subject: RE: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server Is this a more reliable source: https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/date-time-and-timestamp-escape-sequences ? It specifies the same {ts 'yyyy-mm-dd hh:mi:ss.sssss'} as Gerd quoted from Oracle. -- Alexandre Peshansky, MS Lead Bioinformatics Analyst, Research Informatics Core (RIC) Harold & Muriel Block Institute for Clinical & Translational Research at Einstein and Montefiore Albert Einstein College of Medicine 1300 Morris Park Ave, Block Bldg., Rm 534 Bronx, NY 10461 (718) 430-2440, (914) 457-6792 (office) (201) 970-3530 (cell) - NEW!!! -----Original Message----- From: Alex Malmyguine [mailto:ale...@bl...] Sent: Wednesday, June 28, 2017 2:48 PM To: Gerd Wagner; squ...@li...<mailto:squ...@li...> Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server Greg, Why should I look at Oracle docs for MS SQL? Not sure I understand. Obviously, executing this will result in an error in MS SQL: select {ts '2017-02-24 10:56:12.790000'} Msg 241, Level 16, State 3, Line 1 Conversion failed when converting date and/or time from character string. However this works: select '2017-02-24 10:56:12.790' There may be some valid considerations for using the former format, but the statements are generated from MS SQL database, therefore should run in MS SQL correctly whether in Squirrel or any other client. This is not happening - the former format only runs in Squirrel. If I generated a statement in Squirrel, I therefore cannot provide it to another person not using Squirrel, and I cannot save it to source control as no one will be able to apply it. The setting I mentioned should apply to generated timestamps as well. Makes sense? Thank you Alex -----Original Message----- From: Gerd Wagner [mailto:ger...@t-...] Sent: Monday, June 26, 2017 4:30 PM To: Alex Malmyguine; squ...@li...<mailto:squ...@li...> Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server Am 20.06.2017 um 17:08 schrieb Alex Malmyguine: When generating an INSERT-INTO script from the result of a select statement, the DATETIME column values come across as follows: {ts '2017-02-24 10:56:12.790000'} The correct format would be as follows: '2017-02-24 10:56:12.790' No, it isn't. The upper form is correct. See section 13.4.2 of the JDBC specification here: http://download.oracle.com/otndocs/jcp/jdbc-4_2-mrel2-eval-spec/index.html Also, BIT fields come across as 'true' or 'false' which confuses SQL Server when this executes. Can those be changed to 1/0? This should be possible by the help of the MSSQL Plugin. Do you use the plugin. If not please try it out and see if it already works. If not you might want to file a feature request here: https://sourceforge.net/p/squirrel-sql/feature-requests/?source=navbar Gerd ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Squirrel-sql-users mailing list Squ...@li...<mailto:Squ...@li...> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Squirrel-sql-users mailing list Squ...@li...<mailto:Squ...@li...> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users |
|
From: Alex M. <ale...@bl...> - 2017-06-29 13:50:56
|
I could not help but noticed that you modified the timestamp, versus generated by Squirrel, ever so slightly: yours only contains 3 digits for milliseconds.
Converting your statement to an MWE, I can get it to work, but if I add back 3 extra digits for milliseconds, as Squirrel generates, I get an error again. Run this:
declare @APR2010 table ([hire date] datetime)
SELECT *
FROM @APR2010 WHERE [HIRE DATE] > {ts '2010-03-31 00:00:00.000'} -- yours
SELECT *
FROM @APR2010 WHERE [HIRE DATE] > {ts '2010-03-31 00:00:00.000000'} -- Squirrel's
There needs to be a setting for output format of timestamps, as not everyone wants the ODBC TS format, and even searching/replacing in the generated scripts is a tedious task. I assume some code is already roughed in where my screen shot was showing, it only needs to be enhanced to apply to generated outputs.
Thank you!
Alex
-----Original Message-----
From: Alexandre Peshansky [mailto:Ale...@ei...]
Sent: Wednesday, June 28, 2017 4:44 PM
To: Alex Malmyguine
Cc: squ...@li...
Subject: RE: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server
SELECT *
FROM [Dental].[dbo].[APR2010] WHERE [HIRE DATE] > {ts '2010-03-31 00:00:00.000'}
--
Alexandre Peshansky, MS
Lead Bioinformatics Analyst, Research Informatics Core (RIC) Harold & Muriel Block Institute for Clinical & Translational Research at Einstein and Montefiore Albert Einstein College of Medicine
1300 Morris Park Ave, Block Bldg., Rm 534 Bronx, NY 10461
(718) 430-2440, (914) 457-6792 (office) (201) 970-3530 (cell) - NEW!!!
-----Original Message-----
From: Alex Malmyguine [mailto:ale...@bl...]
Sent: Wednesday, June 28, 2017 4:05 PM
To: squ...@li...
Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server
Can you provide an example of a working SQL statement with that as a datetime value, executable in SQL server?
Thank you
Alex
-----Original Message-----
From: Alexandre Peshansky [mailto:Ale...@ei...]
Sent: Wednesday, June 28, 2017 3:50 PM
To: Alex Malmyguine
Cc: squ...@li...
Subject: RE: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server
Is this a more reliable source: https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/date-time-and-timestamp-escape-sequences ?
It specifies the same {ts 'yyyy-mm-dd hh:mi:ss.sssss'} as Gerd quoted from Oracle.
--
Alexandre Peshansky, MS
Lead Bioinformatics Analyst, Research Informatics Core (RIC) Harold & Muriel Block Institute for Clinical & Translational Research at Einstein and Montefiore Albert Einstein College of Medicine
1300 Morris Park Ave, Block Bldg., Rm 534 Bronx, NY 10461
(718) 430-2440, (914) 457-6792 (office) (201) 970-3530 (cell) - NEW!!!
-----Original Message-----
From: Alex Malmyguine [mailto:ale...@bl...]
Sent: Wednesday, June 28, 2017 2:48 PM
To: Gerd Wagner; squ...@li...
Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server
Greg,
Why should I look at Oracle docs for MS SQL? Not sure I understand. Obviously, executing this will result in an error in MS SQL:
select {ts '2017-02-24 10:56:12.790000'}
Msg 241, Level 16, State 3, Line 1
Conversion failed when converting date and/or time from character string.
However this works:
select '2017-02-24 10:56:12.790'
There may be some valid considerations for using the former format, but the statements are generated from MS SQL database, therefore should run in MS SQL correctly whether in Squirrel or any other client. This is not happening - the former format only runs in Squirrel. If I generated a statement in Squirrel, I therefore cannot provide it to another person not using Squirrel, and I cannot save it to source control as no one will be able to apply it. The setting I mentioned should apply to generated timestamps as well.
Makes sense?
Thank you
Alex
-----Original Message-----
From: Gerd Wagner [mailto:ger...@t-...]
Sent: Monday, June 26, 2017 4:30 PM
To: Alex Malmyguine; squ...@li...
Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server
Am 20.06.2017 um 17:08 schrieb Alex Malmyguine:
> When generating an INSERT-INTO script from the result of a select
> statement, the DATETIME column values come across as follows:
>
> {ts '2017-02-24 10:56:12.790000'}
>
> The correct format would be as follows:
>
> '2017-02-24 10:56:12.790'
No, it isn't. The upper form is correct. See section 13.4.2 of the JDBC specification here:
http://download.oracle.com/otndocs/jcp/jdbc-4_2-mrel2-eval-spec/index.html
>
> Also, BIT fields come across as 'true' or 'false' which confuses SQL
> Server when this executes. Can those be changed to 1/0?
This should be possible by the help of the MSSQL Plugin. Do you use the plugin. If not please try it out and see if it already works. If not you might want to file a feature request here:
https://sourceforge.net/p/squirrel-sql/feature-requests/?source=navbar
Gerd
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Squirrel-sql-users mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Squirrel-sql-users mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
|
|
From: Neville R. <row...@ho...> - 2017-06-28 21:41:21
|
Hi Alex, The documents Gerd linked to are the JDBC standard documents as defined by JSR-000221 under the Java Community Process. Those documents define exactly how a JDBC v4.2 driver should operate. According to Microsoft here https://docs.microsoft.com/en-us/sql/connect/jdbc/using-sql-escape-sequences the MS JDBC driver support this escape sequence. We choose to support this in Squirrel since as this is part of the JDBC standard it should work across all JDBC drivers, rather than us having to do something different per driver / database. >> Can you provide an example of a working SQL statement with that as a datetime value, executable in SQL server? When you say ‘executable in SQL server’ - this is a JDBC standard escape sequence, so it is executable in SQL Server so long as the connection to the server is over JDBC. As per the enclosed screenshot of a quick Java test program. Horses for courses - the syntax you had will work on MS SQL Server irrespective of connection type, the syntax SquirrelSQL supports should work on all JDBC connections irrespective of server type. However the problem with the example is the length of the final field - this fails select {ts '2017-02-24 10:56:12.790000’} But this succeeds select {ts '2017-02-24 10:56:12.790'} There is nothing in the spec I can find which talks about the length of that field so this is probably debatable. I’ve always thought of it as milliseconds but I guess this is coming out as microseconds. N. > On 28 Jun 2017, at 21:44, Alexandre Peshansky <Ale...@ei...> wrote: > > SELECT * > FROM [Dental].[dbo].[APR2010] WHERE [HIRE DATE] > {ts '2010-03-31 00:00:00.000'} > > -- > Alexandre Peshansky, MS > Lead Bioinformatics Analyst, Research Informatics Core (RIC) > Harold & Muriel Block Institute for Clinical & Translational Research at Einstein and Montefiore > Albert Einstein College of Medicine > 1300 Morris Park Ave, Block Bldg., Rm 534 Bronx, NY 10461 > (718) 430-2440, (914) 457-6792 (office) (201) 970-3530 (cell) - NEW!!! > > > > -----Original Message----- > From: Alex Malmyguine [mailto:ale...@bl...] > Sent: Wednesday, June 28, 2017 4:05 PM > To: squ...@li... > Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server > > Can you provide an example of a working SQL statement with that as a datetime value, executable in SQL server? > > Thank you > Alex > > -----Original Message----- > From: Alexandre Peshansky [mailto:Ale...@ei...] > Sent: Wednesday, June 28, 2017 3:50 PM > To: Alex Malmyguine > Cc: squ...@li... > Subject: RE: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server > > Is this a more reliable source: https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/date-time-and-timestamp-escape-sequences ? > It specifies the same {ts 'yyyy-mm-dd hh:mi:ss.sssss'} as Gerd quoted from Oracle. > -- > Alexandre Peshansky, MS > Lead Bioinformatics Analyst, Research Informatics Core (RIC) Harold & Muriel Block Institute for Clinical & Translational Research at Einstein and Montefiore Albert Einstein College of Medicine > 1300 Morris Park Ave, Block Bldg., Rm 534 Bronx, NY 10461 > (718) 430-2440, (914) 457-6792 (office) (201) 970-3530 (cell) - NEW!!! > > > > -----Original Message----- > From: Alex Malmyguine [mailto:ale...@bl...] > Sent: Wednesday, June 28, 2017 2:48 PM > To: Gerd Wagner; squ...@li... > Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server > > Greg, > > Why should I look at Oracle docs for MS SQL? Not sure I understand. Obviously, executing this will result in an error in MS SQL: > > select {ts '2017-02-24 10:56:12.790000'} > > Msg 241, Level 16, State 3, Line 1 > Conversion failed when converting date and/or time from character string. > > However this works: > > select '2017-02-24 10:56:12.790' > > There may be some valid considerations for using the former format, but the statements are generated from MS SQL database, therefore should run in MS SQL correctly whether in Squirrel or any other client. This is not happening - the former format only runs in Squirrel. If I generated a statement in Squirrel, I therefore cannot provide it to another person not using Squirrel, and I cannot save it to source control as no one will be able to apply it. The setting I mentioned should apply to generated timestamps as well. > > Makes sense? > > Thank you > Alex > > -----Original Message----- > From: Gerd Wagner [mailto:ger...@t-...] > Sent: Monday, June 26, 2017 4:30 PM > To: Alex Malmyguine; squ...@li... > Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server > > > > Am 20.06.2017 um 17:08 schrieb Alex Malmyguine: >> When generating an INSERT-INTO script from the result of a select >> statement, the DATETIME column values come across as follows: >> >> {ts '2017-02-24 10:56:12.790000'} >> >> The correct format would be as follows: >> >> '2017-02-24 10:56:12.790' > > No, it isn't. The upper form is correct. See section 13.4.2 of the JDBC specification here: > http://download.oracle.com/otndocs/jcp/jdbc-4_2-mrel2-eval-spec/index.html > >> >> Also, BIT fields come across as 'true' or 'false' which confuses SQL >> Server when this executes. Can those be changed to 1/0? > This should be possible by the help of the MSSQL Plugin. Do you use the plugin. If not please try it out and see if it already works. If not you might want to file a feature request here: > https://sourceforge.net/p/squirrel-sql/feature-requests/?source=navbar > > Gerd > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Squirrel-sql-users mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Squirrel-sql-users mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Squirrel-sql-users mailing list > Squ...@li... > https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users |
|
From: John H. <jh...@im...> - 2017-06-28 21:36:36
|
On Wed, 28 Jun 2017, Alexandre Peshansky wrote:
> SELECT *
> FROM [Dental].[dbo].[APR2010] WHERE [HIRE DATE] > {ts '2010-03-31 00:00:00.000'}
Or even just:
SELECT {ts '2010-03-31 00:00:00.000'};
...works. Learn something new every day...
However, I too get this result:
> select {ts '2017-02-24 10:56:12.790000'}
>
> Msg 241, Level 16, State 3, Line 1
> Conversion failed when converting date and/or time from character string.
...which, along with getting errors in Squirrel from generated INSERT
statements, supported my assumption that the {ts} format was an annoying
JDBC-ism.
As it turns out, MSSQL only allows three decimal places in the fractional
time part. This works:
SELECT {ts '2017-02-24 10:56:12.790'}
...so it isn't *exactly* as documented by 'Orrible for JDBC or MSFT for
ODBC.
Perhaps Squirrel needs to be made aware of the decimal places limit so
that it can generate working timestamps when querying from MSSQL?
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jh...@im... FALaholic #11174 pgpk -a jh...@im...
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
USMC Rules of Gunfighting #7: In ten years nobody will remember
the details of caliber, stance, or tactics. They will only remember
who lived.
-----------------------------------------------------------------------
6 days until the 241st anniversary of the Declaration of Independence
|
|
From: Alexandre P. <Ale...@ei...> - 2017-06-28 21:23:36
|
Is this a more reliable source: https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/date-time-and-timestamp-escape-sequences ? It specifies the same {ts 'yyyy-mm-dd hh:mi:ss.sssss'} as Gerd quoted from Oracle. -- Alexandre Peshansky, MS Lead Bioinformatics Analyst, Research Informatics Core (RIC) Harold & Muriel Block Institute for Clinical & Translational Research at Einstein and Montefiore Albert Einstein College of Medicine 1300 Morris Park Ave, Block Bldg., Rm 534 Bronx, NY 10461 (718) 430-2440, (914) 457-6792 (office) (201) 970-3530 (cell) - NEW!!! -----Original Message----- From: Alex Malmyguine [mailto:ale...@bl...] Sent: Wednesday, June 28, 2017 2:48 PM To: Gerd Wagner; squ...@li... Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server Greg, Why should I look at Oracle docs for MS SQL? Not sure I understand. Obviously, executing this will result in an error in MS SQL: select {ts '2017-02-24 10:56:12.790000'} Msg 241, Level 16, State 3, Line 1 Conversion failed when converting date and/or time from character string. However this works: select '2017-02-24 10:56:12.790' There may be some valid considerations for using the former format, but the statements are generated from MS SQL database, therefore should run in MS SQL correctly whether in Squirrel or any other client. This is not happening - the former format only runs in Squirrel. If I generated a statement in Squirrel, I therefore cannot provide it to another person not using Squirrel, and I cannot save it to source control as no one will be able to apply it. The setting I mentioned should apply to generated timestamps as well. Makes sense? Thank you Alex -----Original Message----- From: Gerd Wagner [mailto:ger...@t-...] Sent: Monday, June 26, 2017 4:30 PM To: Alex Malmyguine; squ...@li... Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server Am 20.06.2017 um 17:08 schrieb Alex Malmyguine: > When generating an INSERT-INTO script from the result of a select > statement, the DATETIME column values come across as follows: > > {ts '2017-02-24 10:56:12.790000'} > > The correct format would be as follows: > > '2017-02-24 10:56:12.790' No, it isn't. The upper form is correct. See section 13.4.2 of the JDBC specification here: http://download.oracle.com/otndocs/jcp/jdbc-4_2-mrel2-eval-spec/index.html > > Also, BIT fields come across as 'true' or 'false' which confuses SQL > Server when this executes. Can those be changed to 1/0? This should be possible by the help of the MSSQL Plugin. Do you use the plugin. If not please try it out and see if it already works. If not you might want to file a feature request here: https://sourceforge.net/p/squirrel-sql/feature-requests/?source=navbar Gerd ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Squirrel-sql-users mailing list Squ...@li... https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users |
|
From: Alexandre P. <Ale...@ei...> - 2017-06-28 21:01:04
|
SELECT *
FROM [Dental].[dbo].[APR2010] WHERE [HIRE DATE] > {ts '2010-03-31 00:00:00.000'}
--
Alexandre Peshansky, MS
Lead Bioinformatics Analyst, Research Informatics Core (RIC)
Harold & Muriel Block Institute for Clinical & Translational Research at Einstein and Montefiore
Albert Einstein College of Medicine
1300 Morris Park Ave, Block Bldg., Rm 534 Bronx, NY 10461
(718) 430-2440, (914) 457-6792 (office) (201) 970-3530 (cell) - NEW!!!
-----Original Message-----
From: Alex Malmyguine [mailto:ale...@bl...]
Sent: Wednesday, June 28, 2017 4:05 PM
To: squ...@li...
Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server
Can you provide an example of a working SQL statement with that as a datetime value, executable in SQL server?
Thank you
Alex
-----Original Message-----
From: Alexandre Peshansky [mailto:Ale...@ei...]
Sent: Wednesday, June 28, 2017 3:50 PM
To: Alex Malmyguine
Cc: squ...@li...
Subject: RE: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server
Is this a more reliable source: https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/date-time-and-timestamp-escape-sequences ?
It specifies the same {ts 'yyyy-mm-dd hh:mi:ss.sssss'} as Gerd quoted from Oracle.
--
Alexandre Peshansky, MS
Lead Bioinformatics Analyst, Research Informatics Core (RIC) Harold & Muriel Block Institute for Clinical & Translational Research at Einstein and Montefiore Albert Einstein College of Medicine
1300 Morris Park Ave, Block Bldg., Rm 534 Bronx, NY 10461
(718) 430-2440, (914) 457-6792 (office) (201) 970-3530 (cell) - NEW!!!
-----Original Message-----
From: Alex Malmyguine [mailto:ale...@bl...]
Sent: Wednesday, June 28, 2017 2:48 PM
To: Gerd Wagner; squ...@li...
Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server
Greg,
Why should I look at Oracle docs for MS SQL? Not sure I understand. Obviously, executing this will result in an error in MS SQL:
select {ts '2017-02-24 10:56:12.790000'}
Msg 241, Level 16, State 3, Line 1
Conversion failed when converting date and/or time from character string.
However this works:
select '2017-02-24 10:56:12.790'
There may be some valid considerations for using the former format, but the statements are generated from MS SQL database, therefore should run in MS SQL correctly whether in Squirrel or any other client. This is not happening - the former format only runs in Squirrel. If I generated a statement in Squirrel, I therefore cannot provide it to another person not using Squirrel, and I cannot save it to source control as no one will be able to apply it. The setting I mentioned should apply to generated timestamps as well.
Makes sense?
Thank you
Alex
-----Original Message-----
From: Gerd Wagner [mailto:ger...@t-...]
Sent: Monday, June 26, 2017 4:30 PM
To: Alex Malmyguine; squ...@li...
Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server
Am 20.06.2017 um 17:08 schrieb Alex Malmyguine:
> When generating an INSERT-INTO script from the result of a select
> statement, the DATETIME column values come across as follows:
>
> {ts '2017-02-24 10:56:12.790000'}
>
> The correct format would be as follows:
>
> '2017-02-24 10:56:12.790'
No, it isn't. The upper form is correct. See section 13.4.2 of the JDBC specification here:
http://download.oracle.com/otndocs/jcp/jdbc-4_2-mrel2-eval-spec/index.html
>
> Also, BIT fields come across as 'true' or 'false' which confuses SQL
> Server when this executes. Can those be changed to 1/0?
This should be possible by the help of the MSSQL Plugin. Do you use the plugin. If not please try it out and see if it already works. If not you might want to file a feature request here:
https://sourceforge.net/p/squirrel-sql/feature-requests/?source=navbar
Gerd
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Squirrel-sql-users mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Squirrel-sql-users mailing list
Squ...@li...
https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users
|
|
From: Alex M. <ale...@bl...> - 2017-06-28 20:04:49
|
Can you provide an example of a working SQL statement with that as a datetime value, executable in SQL server? Thank you Alex -----Original Message----- From: Alexandre Peshansky [mailto:Ale...@ei...] Sent: Wednesday, June 28, 2017 3:50 PM To: Alex Malmyguine Cc: squ...@li... Subject: RE: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server Is this a more reliable source: https://docs.microsoft.com/en-us/sql/odbc/reference/appendixes/date-time-and-timestamp-escape-sequences ? It specifies the same {ts 'yyyy-mm-dd hh:mi:ss.sssss'} as Gerd quoted from Oracle. -- Alexandre Peshansky, MS Lead Bioinformatics Analyst, Research Informatics Core (RIC) Harold & Muriel Block Institute for Clinical & Translational Research at Einstein and Montefiore Albert Einstein College of Medicine 1300 Morris Park Ave, Block Bldg., Rm 534 Bronx, NY 10461 (718) 430-2440, (914) 457-6792 (office) (201) 970-3530 (cell) - NEW!!! -----Original Message----- From: Alex Malmyguine [mailto:ale...@bl...] Sent: Wednesday, June 28, 2017 2:48 PM To: Gerd Wagner; squ...@li... Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server Greg, Why should I look at Oracle docs for MS SQL? Not sure I understand. Obviously, executing this will result in an error in MS SQL: select {ts '2017-02-24 10:56:12.790000'} Msg 241, Level 16, State 3, Line 1 Conversion failed when converting date and/or time from character string. However this works: select '2017-02-24 10:56:12.790' There may be some valid considerations for using the former format, but the statements are generated from MS SQL database, therefore should run in MS SQL correctly whether in Squirrel or any other client. This is not happening - the former format only runs in Squirrel. If I generated a statement in Squirrel, I therefore cannot provide it to another person not using Squirrel, and I cannot save it to source control as no one will be able to apply it. The setting I mentioned should apply to generated timestamps as well. Makes sense? Thank you Alex -----Original Message----- From: Gerd Wagner [mailto:ger...@t-...] Sent: Monday, June 26, 2017 4:30 PM To: Alex Malmyguine; squ...@li... Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server Am 20.06.2017 um 17:08 schrieb Alex Malmyguine: > When generating an INSERT-INTO script from the result of a select > statement, the DATETIME column values come across as follows: > > {ts '2017-02-24 10:56:12.790000'} > > The correct format would be as follows: > > '2017-02-24 10:56:12.790' No, it isn't. The upper form is correct. See section 13.4.2 of the JDBC specification here: http://download.oracle.com/otndocs/jcp/jdbc-4_2-mrel2-eval-spec/index.html > > Also, BIT fields come across as 'true' or 'false' which confuses SQL > Server when this executes. Can those be changed to 1/0? This should be possible by the help of the MSSQL Plugin. Do you use the plugin. If not please try it out and see if it already works. If not you might want to file a feature request here: https://sourceforge.net/p/squirrel-sql/feature-requests/?source=navbar Gerd ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Squirrel-sql-users mailing list Squ...@li... https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users |
|
From: Alex M. <ale...@bl...> - 2017-06-28 18:48:13
|
Greg,
Why should I look at Oracle docs for MS SQL? Not sure I understand. Obviously, executing this will result in an error in MS SQL:
select {ts '2017-02-24 10:56:12.790000'}
Msg 241, Level 16, State 3, Line 1
Conversion failed when converting date and/or time from character string.
However this works:
select '2017-02-24 10:56:12.790'
There may be some valid considerations for using the former format, but the statements are generated from MS SQL database, therefore should run in MS SQL correctly whether in Squirrel or any other client. This is not happening - the former format only runs in Squirrel. If I generated a statement in Squirrel, I therefore cannot provide it to another person not using Squirrel, and I cannot save it to source control as no one will be able to apply it. The setting I mentioned should apply to generated timestamps as well.
Makes sense?
Thank you
Alex
-----Original Message-----
From: Gerd Wagner [mailto:ger...@t-...]
Sent: Monday, June 26, 2017 4:30 PM
To: Alex Malmyguine; squ...@li...
Subject: Re: [Squirrel-sql-users] Date/time format in the generated insert into script for SQL Server
Am 20.06.2017 um 17:08 schrieb Alex Malmyguine:
> When generating an INSERT-INTO script from the result of a select
> statement, the DATETIME column values come across as follows:
>
> {ts '2017-02-24 10:56:12.790000'}
>
> The correct format would be as follows:
>
> '2017-02-24 10:56:12.790'
No, it isn't. The upper form is correct. See section 13.4.2 of the JDBC specification here:
http://download.oracle.com/otndocs/jcp/jdbc-4_2-mrel2-eval-spec/index.html
>
> Also, BIT fields come across as 'true' or 'false' which confuses SQL
> Server when this executes. Can those be changed to 1/0?
This should be possible by the help of the MSSQL Plugin. Do you use the plugin. If not please try it out and see if it already works. If not you might want to file a feature request here:
https://sourceforge.net/p/squirrel-sql/feature-requests/?source=navbar
Gerd
|
|
From: Gerd W. <ger...@t-...> - 2017-06-26 20:29:49
|
Am 20.06.2017 um 17:08 schrieb Alex Malmyguine:
> When generating an INSERT-INTO script from the result of a select
> statement, the DATETIME column values come across as follows:
>
> {ts '2017-02-24 10:56:12.790000'}
>
> The correct format would be as follows:
>
> '2017-02-24 10:56:12.790'
No, it isn't. The upper form is correct. See section 13.4.2 of the JDBC
specification here:
http://download.oracle.com/otndocs/jcp/jdbc-4_2-mrel2-eval-spec/index.html
>
> Also, BIT fields come across as 'true' or 'false' which confuses SQL
> Server when this executes. Can those be changed to 1/0?
This should be possible by the help of the MSSQL Plugin. Do you use the
plugin. If not please try it out and see if it already works. If not you
might want to file a feature request here:
https://sourceforge.net/p/squirrel-sql/feature-requests/?source=navbar
Gerd
|
|
From: John H. <jh...@im...> - 2017-06-25 19:07:39
|
On Sat, 24 Jun 2017, Hotovaga wrote: > I use MS SQL, and they are different. > However, there is a link in microsoft site for downloading JDBC. Buy > SquirreL requires JDBC ODBC Bridge,If I download JDBC from Microsoft site, > will that do? Squirrel *does not* require a JDBC/ODBC bridge to access MSSQL. Just download the current MSSQL JDBC driver and use it directly. It works perfectly, including encryption. I use it every day. -- John Hardin KA7OHZ http://www.impsec.org/~jhardin/ jh...@im... FALaholic #11174 pgpk -a jh...@im... key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 ----------------------------------------------------------------------- One unexpected benefit of time passing more quickly as you get older is the perceived increase in the frequency of paychecks. ----------------------------------------------------------------------- 9 days until the 241st anniversary of the Declaration of Independence |
|
From: Neville R. <row...@ho...> - 2017-06-25 14:13:04
|
Hi Hotovaga, If you are using MS SQL Server, then Microsoft provide a recommended JDBC driver here https://docs.microsoft.com/en-us/sql/connect/jdbc/microsoft-jdbc-driver-for-sql-server Neville On 24 Jun 2017, at 21:58, Hotovaga <mok...@gm...<mailto:mok...@gm...>> wrote: hi buttcahes, thank you, again for your attention to tjis matter I sincerely appreciate your willingness to help. I checked the link you o]provided, but it only allows access to MS Access ("to read/write Microsoft Access databases.") I use MS SQL, and they are different. However, there is a link in microsoft site for downloading JDBC. Buy SquirreL requires JDBC ODBC Bridge,If I download JDBC from Microsoft site, will that do? Thanks again. -- View this message in context: http://squirrel-sql-client.10976.n7.nabble.com/JDBCODBC-Bridge-driver-tp3808p3822.html Sent from the Users mailing list archive at Nabble.com<http://Nabble.com>. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org<http://Slashdot.org>! http://sdm.link/slashdot _______________________________________________ Squirrel-sql-users mailing list Squ...@li...<mailto:Squ...@li...> https://lists.sourceforge.net/lists/listinfo/squirrel-sql-users |
