Taro L. Saito
unread,Nov 12, 2009, 6:10:14 AM11/12/09Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Xerial
Hi all,
Now that I added a support for 64-bit native libraries, I'm
considering to drop the pure-java support of SQLite from sqlite-jdbc.
This is mainly because I get tired to build the pure-java version of
SQLite.
For example, I have encountered the following troubles:
- I failed to build nestedVM on Mac OS X 10.6 (SnowLeopard), which is
necessary to build pure-java SQLite.
- the behavior of pure-java version is different between Win and Mac,
especially when executing transactions.
I guess native libraries of SQLIte for Win(32/64-bit), Mac OS X(32/64-
bit), and Linux(i386/amd64) cover the major platforms.
In Linux, you still have to rebuild sqlite-jdbc from scratch if glibc
version is different between where I built the sqlite-jdbc and your
Linux.
Pure-java mode provides a little safety, but its speed is too slow,
thus the benefit we can achieve is quite low, considering the
time I have to spend to build the pure-java SQLite, which needs to
build gcc-3.x from scratch, and also we have to modify the source code
of the original SQLite.
If the problems I mentioned above cannot be fixed, I would like to
drop pure-java support,
or to continue to use pure-java version of older version of sqlite
(e.g. sqlite 3.6.17, which is built successfully)
along with the native libraries of newer versions.
For example, sqlite-jdbc-3.6.xx release will contain sqlite 3.6.xx
native libraries for Win, Mac and Linux. For the other environments,
pure-java version of sqlite-3.6.17 will be used.
Your opinion is welcome.