RawrUniversal / xerial

Automatically exported from code.google.com/p/xerial
0 stars 1 forks source link

localtime modifier does not work when run against 64-bit Java 6 on OS X. #24

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

1. Store an ISO-8601 date string like "2009-09-04T03:00:00Z" in a column.
2. Query the date using the localtime modifier, e.g. "select datetime(Date,
'localtime') from Dates"

What is the expected output? What do you see instead?

In my timezone, PDT (-7 hours), I see "2009-09-03 20:00:00" on most
systems.  Using Java 6 (64-bit) on OS X however, I see "2009-09-04 03:00:00"

What version of the product are you using? On what operating system?
sqlite-jdbc-3.6.17.1.jar, on Windows Vista with JDK-6 u16 and OS X 10.5.8
with Java 5 (32-bit) and Java 6 (64-bit)

Original issue reported on code.google.com by mmcnabb...@gmail.com on 5 Sep 2009 at 1:32

GoogleCodeExporter commented 8 years ago

Original comment by taroleo on 10 Sep 2009 at 5:56

GoogleCodeExporter commented 8 years ago
After getting the 3.6.17.1 sources using svn, I compiled a 64-bit jni library 
for OS
X and added it to the jar as native/Mac/x86_64/libsqlitejdbc.jnilib.  This 
seemed to
fix the problem when running with 64-bit java, as it was then able to run 
sqlite-jdbc
in native mode instead of pure mode.   So I guess the bug here is specific to 
using
pure mode in 64-bit Java.

I recommend including an x86-64 version of the OS X jnilib in future releases.  
In OS
X 10.6, 64-bit Java 6 is the only version available.

Thanks very much for maintaining this.  It is extremely useful.

Original comment by mmcnabb...@gmail.com on 14 Sep 2009 at 5:57

GoogleCodeExporter commented 8 years ago
I will fix this problem by adding a 64-bit binary for OS X. 

Original comment by taroleo on 25 Sep 2009 at 10:16

GoogleCodeExporter commented 8 years ago
changed the milestone

Original comment by taroleo on 25 Nov 2009 at 11:50

GoogleCodeExporter commented 8 years ago
This issue was closed by revision 7eb6b01399.

Original comment by taroleo on 8 Dec 2009 at 6:29