Greetings everyone.
I have searched a bit how to use SQLite's latest version in Java and
unfortunately did not find anything other than SQLiteJDBC (which is really
outdated) and sqlite4java (which has not released any update for about a year
now).
I feel a bit bittered with the way Java is
On Fri, Jun 29, 2012 at 8:36 AM, stefanos sofroniou
stefanossofroniou...@yahoo.com wrote:
I have searched a bit how to use SQLite's latest version in Java and
unfortunately did not find anything other than SQLiteJDBC (which is really
outdated) and sqlite4java (which has not released any
Ok, back on this topic.
I've discovered one issue that is possibly the cause of this whole
weirdness, but I can't explain what's going on. Perhaps someone has seen
this happen.
What I found is that after I delete the database file (using Windows
explorer or from the command-line, doesn't
On 29 Jun 2012, at 11:11am, Peter Volkis petervol...@yahoo.com wrote:
My question is about a complete list [snip]
It'll never happen. Nobody knows who uses SQLite in one of their products.
The only reason people know I use SQLite is I'm not a brilliant programmer so
I've had to ask
On 29 Jun 2012, at 11:57am, Dennis Volodomanov i...@psunrise.com wrote:
What I found is that after I delete the database file (using Windows explorer
or from the command-line, doesn't matter - this is all on Windows 7 x64) and
then let my application re-create it as normal, it already
On 29/06/2012 9:25 PM, Simon Slavin wrote:
Your app or the shell tool is running while you delete the file, or do you
quit, delete, then restart them ?
When you specify the database file to open are you specifying a full path, from
the 'C:\' on down, or are you relying on some default folder
On 29.06.2012 13:42, Dennis Volodomanov wrote:
On 29/06/2012 9:25 PM, Simon Slavin wrote:
Your app or the shell tool is running while you delete the file, or do you
quit, delete, then restart them ?
When you specify the database file to open are you specifying a full path, from
the 'C:\'
Ok, tried using the shell and the result is the same as using my app.
What I did is:
1) delete the database file (mydbname.ext) from the DOS prompt, make
sure the file is not there
2) run sqlite3 .\mydbname.ext from within that same folder, same DOS
prompt
3) type .dump
4) see entries in
On 29/06/2012 9:45 PM, Marcus Grimm wrote:
Just a quess: Are you using wal mode ?
And how to you delete the DB ? Are you removing also any journal or
-wal files (if any) ?
Yes, WAL mode and I do clear out all files.
Dennis
___
sqlite-users
On 29 Jun 2012, at 12:47pm, Dennis Volodomanov i...@psunrise.com wrote:
Ok, tried using the shell and the result is the same as using my app.
What I did is:
1) delete the database file (mydbname.ext) from the DOS prompt, make sure
the file is not there
2) run sqlite3 .\mydbname.ext
Marc L. Allen mlallen at outsitenetworks.com Thu Jun 28 09:31:40 EDT 2012
I think he wants to know why he is receiving what appears to be an error
notification via the callback.
Adam DeVita adevita at verifeye.com Thu Jun 28 09:04:44 EDT 2012
What is the problem?
Yes, the error message through
Igor Tandetnik itandetnik at mvps.org Thu Jun 28 09:38:27 EDT 2012
My guess is that a) you have prepared your statement with
sqlite3_prepare_v2 (as opposed to sqlite3_prepare)...
Statement was prepared with sqlite3_prepare16_v2()
Database file was created only moments earlier.
Jeff Archer
License details are here:
http://www.sqlite.org/copyright.html
tl;dr version: no license is required or even requested. You can buy one if
some part of your organisation requires it for legal purposes.
I am aware of this, I have visited sqlite.org before asking on the mailing list.
There's
Care to show all of your steps? Not that my BS flag is waving but you're
correct that this is very odd.
What OS?
What version sqlite?
Shell from website or did you compile?
Local file?
Does it persist across a reboot?
Are you running ANY 3rd party software?
Try uninstalling your
You need to ask your question betteryour example will give an answer but I
have no idea what answer you are looking for.
Can you give a complete example?
CREATE TABLE TableA(z);
INSERT INTO TableA VALUES(2.0);
INSERT INTO TableA VALUES(4.0);
INSERT INTO TableA VALUES(8.0);
INSERT INTO
On 29/06/2012 9:52 PM, Simon Slavin wrote:
When you're deleting the database file, look for any other files in the same folder with
names that start with mydbname and anything after that, including any
extension. (Marcus's theory) Tell us what they're called.
Make sure you're quitting the
Michael,
It works using the shell with one simple table, so I'm investigating
this further to see if I can get this to break using the shell (by
adding pragmas, triggers, indexes, from my code). This is on a new file
in a different folder to the other test.
The OS is Windows 7 x64, SQLite
Hiho,
FYI: sqlite4.h is being generated with an unclosed comment on line 3443:
/*
**
/*
** CAPIREF: Mutexes
*/
it also has the long-standing 'long long' c89 incompatibility, but that's
only significant if c89 is a hard goal (which it isn't, from what i
understand).
--
- stephan
To further confuse things:
I've deleted all files from that old folder. Then using the shell:
sqlite3 mydb.ext and .dump - shows the usual rubbish. The
interesting bit here now is that there is no mydb.ext file in that
folder (checked using a second command prompt), but there are
It persists across a reboot?
You can create a database, delete it, reboot, and your app will still see the
original table?
All I can say is wow...your system is really hosed.
Even anti-virus shouldn't cause that. This would infer some sort of caching
that is semi-permanent.
Have you got
Hi again,
from sqlite4.h:
_SQLITE3RTREE_H_
collides with sqlite3.h, causing ODR violations when both headers are
included (as is the case in my abstraction layer's amalgamation build).
i've patched that locally but now i'm seeing similar collisions with other
symbols:
Bummer. These are going to be hard to fix. :-(
On Fri, Jun 29, 2012 at 10:21 AM, Stephan Beal sgb...@googlemail.comwrote:
Hi again,
from sqlite4.h:
_SQLITE3RTREE_H_
collides with sqlite3.h, causing ODR violations when both headers are
included (as is the case in my abstraction layer's
On Fri, Jun 29, 2012 at 4:25 PM, Richard Hipp d...@sqlite.org wrote:
Bummer. These are going to be hard to fix. :-(
i guessed that would be the case for some of the long-standing symbols like
SQLITE_OK.
i will admit that including both 3 and 4 into one client is an odd
corner-case.
--
On Fri, Jun 29, 2012 at 4:27 PM, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Jun 29, 2012 at 4:25 PM, Richard Hipp d...@sqlite.org wrote:
Bummer. These are going to be hard to fix. :-(
i guessed that would be the case for some of the long-standing symbols
like SQLITE_OK.
Maybe
On Fri, Jun 29, 2012 at 10:27 AM, Stephan Beal sgb...@googlemail.comwrote:
On Fri, Jun 29, 2012 at 4:25 PM, Richard Hipp d...@sqlite.org wrote:
Bummer. These are going to be hard to fix. :-(
i guessed that would be the case for some of the long-standing symbols like
SQLITE_OK.
i will
You need to check your file system.
When you run the shell doing this on a new, empty directory (this is using the
shell from the website)
sqlite3 mydb.ext
In another window you should NOT see anything.
then after doing .dump you should see a 0-length mydb.ext file appear.
.quit --
On Fri, Jun 29, 2012 at 4:30 PM, Richard Hipp d...@sqlite.org wrote:
Maybe the thing to do is globally replace SQLITE_ with SQLITE4_?
That would be my preference, but it admittedly makes porting more
difficult, and i wouldn't cry too much if you decide to punt on this
problem. i'm working
On Fri, Jun 29, 2012 at 10:32 AM, Stephan Beal sgb...@googlemail.comwrote:
On Fri, Jun 29, 2012 at 4:30 PM, Richard Hipp d...@sqlite.org wrote:
Maybe the thing to do is globally replace SQLITE_ with SQLITE4_?
That would be my preference, but it admittedly makes porting more
difficult,
On Fri, Jun 29, 2012 at 4:33 PM, Richard Hipp d...@sqlite.org wrote:
You think? You already need to do a global search/replace of sqlite3_ to
sqlite4_. How much harder is it to do a separate search/replace of
SQLITE_ to SQLITE4_?
True enough. The only points which i came across not yet
On Fri, Jun 29, 2012 at 4:38 PM, Stephan Beal sgb...@googlemail.com wrote:
Other than that i simply did s/sqlite3/sqlite4/g and all went just fine
One more tiny thing: the build flags for gcc should include -fPIC. Some
Linuxes won't link against a lib built without -fPIC.
--
- stephan
On 30/06/2012 12:19 AM, Black, Michael (IS) wrote:
It persists across a reboot?
You can create a database, delete it, reboot, and your app will still
see the original table?
All I can say is wow...your system is really hosed.
Even anti-virus shouldn't cause that. This would infer some
On Fri, Jun 29, 2012 at 4:38 PM, Stephan Beal sgb...@googlemail.com wrote:
Other than that i simply did s/sqlite3/sqlite4/g and all went just fine,
so i wouldn't expect any problems with s/SQLITE_/SQLITE4_/g.
This actually works.
Here's what i did (incrementally via trial/error), from the
On Fri, Jun 29, 2012 at 11:08 AM, Stephan Beal sgb...@googlemail.comwrote:
On Fri, Jun 29, 2012 at 4:38 PM, Stephan Beal sgb...@googlemail.com
wrote:
Other than that i simply did s/sqlite3/sqlite4/g and all went just fine,
so i wouldn't expect any problems with s/SQLITE_/SQLITE4_/g.
Hiho,
sqliteInt.h: sqlite4_env:
sqlite4_mutex *pFactoryMutex; /* Mutex for pFactory */
is missing from the definition in global.c, line 172. Adding a NULL
there resolves excess initializer warnings and the follow-up errors such
as braces around scalar initializer in nowValue[].
Make test
There is a bug that I've read about on a Windows machines sporting the
NTFS filesystem that when a file is deleted and recreated within a certain
period of time, the original file is retrieved rather than a new one.
On Fri, Jun 29, 2012 at 10:54 AM, Dennis Volodomanov i...@psunrise.comwrote:
On
On Fri, Jun 29, 2012 at 5:42 PM, Richard Hipp d...@sqlite.org wrote:
I also had to change a couple of 7's to 8's in ctime.c (since SQLITE_ is
7 characters long whereas SQLITE4_ is 8). But that plus your changes
above seem to do the trick. The changes are now checked in on the trunk.
Thanks.
On Fri, Jun 29, 2012 at 5:50 PM, Stephan Beal sgb...@googlemail.com wrote:
caused by an unclosed /*, and the long-long (C++-specific) warning, but
other than that everything looks good as far as i'm concerned.
One more bit of pedanticness:
lsmInt.h:35:
#else
# define LSM_DEBUG
#endif
On Fri, Jun 29, 2012 at 5:45 PM, Stephan Beal sgb...@googlemail.com wrote:
sqliteInt.h: sqlite4_env:
sqlite4_mutex *pFactoryMutex; /* Mutex for pFactory */
is missing from the definition in global.c, line 172. Adding a NULL
there resolves excess initializer warnings and the follow-up
Not supposed to be the contentsjust attributes...
Also note the 15-second default time window. If you do it faster than 15
seconds you won't see the effect.
http://support.microsoft.com/kb/172190
http://dfstream.blogspot.com/2012/02/file-system-tunneling-in-windows.html
Not sure if
On Fri, Jun 29, 2012 at 12:01 PM, Stephan Beal sgb...@googlemail.comwrote:
On Fri, Jun 29, 2012 at 5:45 PM, Stephan Beal sgb...@googlemail.com
wrote:
sqliteInt.h: sqlite4_env:
sqlite4_mutex *pFactoryMutex; /* Mutex for pFactory */
is missing from the definition in global.c,
Hey Dan, thanks for that link, it was just what I was looking for.
Yes indeed, someone, somewhere in my software stack is incorrectly mapping out
BLOBs as text.
___
sqlite-users mailing list
sqlite-users@sqlite.org
On Fri, Jun 29, 2012 at 6:04 PM, Richard Hipp d...@sqlite.org wrote:
No. It has been leaking memory for a while now. I need to get to the
bottom of that
If i can be of any assistance, i'm free to help this weekend. i feel kinda
bad about spamming the user list so much, though :/. Should
On 29 Jun 2012, at 3:54pm, Dennis Volodomanov i...@psunrise.com wrote:
Most likely - it is my box that's causing this. Unless SQLite does any sort
of real low-level disk access, bypassing standard OS, then it's unlikely that
it somehow caused this to happen, but it would be good to rule
On Jun 28, 2012, at 5:57 PM, Simon Slavin wrote:
SQLite4 is an alternative, not a replacement, for SQLite3. SQLite3 is not
going away.
Argh… but more seriously… would that new incarnation provide proper error
messages for constraint violations?
Providing a proper data dictionary
On Fri, Jun 29, 2012 at 9:27 AM, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Jun 29, 2012 at 4:25 PM, Richard Hipp d...@sqlite.org wrote:
Bummer. These are going to be hard to fix. :-(
i guessed that would be the case for some of the long-standing symbols like
SQLITE_OK.
i will
On Fri, Jun 29, 2012 at 7:24 PM, Nico Williams n...@cryptonector.comwrote:
I'd be more concerned about linker symbol colliosions than about C
pre-processor symbol collisions.
We have since resolved it - the current code can be compiled with and
linked with both APIs in the same compilation
On June 28, 2012 09:46:06 PDT, Stephan Beal wrote:
- There are no standard printf()/scanf() specifiers for it, which
means
those funcs cannot be used with size_t or ifdefs or casts are needed
to
handle them portably.
Perhaps you should actually check the standard before making such a
On Fri, Jun 29, 2012 at 8:56 PM, Kyle McKay mack...@gmail.com wrote:
On June 28, 2012 09:46:06 PDT, Stephan Beal wrote:
- There are no standard printf()/scanf() specifiers for it, which means
those funcs cannot be used with size_t or ifdefs or casts are needed to
handle them portably.
On 6/29/2012 1:56 PM, Kyle McKay wrote:
On June 28, 2012 09:46:06 PDT, Stephan Beal wrote:
- There are no standard printf()/scanf() specifiers for it, which means
those funcs cannot be used with size_t or ifdefs or casts are needed to
handle them portably.
Perhaps you should actually check
Hello, We are using SQLITE 3.7.10 C/C++ interface API in our product. This is
the very first time we use it. Our product runs on Windows, Linux and
Solaris. We ran into a problem that a query on a 64 bit integer key is
successful on both Windows and Linux, but not on Solaris 10.
On Fri, Jun 29, 2012 at 12:30 PM, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Jun 29, 2012 at 7:24 PM, Nico Williams n...@cryptonector.comwrote:
I'd be more concerned about linker symbol colliosions than about C
pre-processor symbol collisions.
We have since resolved it - the current
So, if I understand section 3.2 of the SQLite4 design page then it
will often be the case that lookup keys will not be stored in an order
that will be useful for optimizing common ORDER BY expressions. Is
this correct? If so, is this worth the trade-off for the single
key/value storage
On Fri, Jun 29, 2012 at 3:40 PM, Nico Williams n...@cryptonector.comwrote:
So, if I understand section 3.2 of the SQLite4 design page then it
will often be the case that lookup keys will not be stored in an order
that will be useful for optimizing common ORDER BY expressions. Is
this
FWIW, every recent release of SQLite has been tested on SunOS 5.10 (Sparc)
using GCC. That doesn't really answer your question (I don't know the real
answer) but it does at least demonstrate that SQLite has been made to work
correctly on Sparc and on SunOS.
On Fri, Jun 29, 2012 at 3:17 PM, Pam
On Fri, Jun 29, 2012 at 2:48 PM, Richard Hipp d...@sqlite.org wrote:
On Fri, Jun 29, 2012 at 3:40 PM, Nico Williams n...@cryptonector.comwrote:
So, if I understand section 3.2 of the SQLite4 design page then it
will often be the case that lookup keys will not be stored in an order
that will be
Thanks for the qucik answer. Looks like our compilers are different. We use
CC. Which version of GCC do you use? Thanks again,pam
From: d...@sqlite.org
Date: Fri, 29 Jun 2012 15:51:35 -0400
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] sqlite3_bind_int64() on Solaris 10?
FWIW,
On Fri, Jun 29, 2012 at 4:22 PM, Pam Li pam...@hotmail.com wrote:
Thanks for the qucik answer. Looks like our compilers are different. We
use CC. Which version of GCC do you use? Thanks again,pam
Tested with GCC 4.3.3.
From: d...@sqlite.org
Date: Fri, 29 Jun 2012 15:51:35 -0400
On Fri, Jun 29, 2012 at 3:26 PM, Jeff Archer jarch...@yahoo.com wrote:
I have been puzzling on this for a couple of days now and am at a loss. I
hate to let something like this go because it appears so much like an
error, I feel like it will just bite me at a later time.
Any suggestions
Kevin Benson kevin.m.benson at gmail.com Fri Jun 29 16:32:55 EDT 2012
The mention of SQLITE_SCHEMA error and sqlite3VdbeExec() sounds like maybe
you're fighting an expired statement???
Not likely. I do Prepare, Bind, Step, Finalize using a wrapper function.
The database file was created only
On Fri, Jun 29, 2012 at 4:55 PM, Jeff Archer jarch...@yahoo.com wrote:
Kevin Benson kevin.m.benson at gmail.com Fri Jun 29 16:32:55 EDT 2012
The mention of SQLITE_SCHEMA error and sqlite3VdbeExec() sounds like maybe
you're fighting an expired statement???
Not likely. I do Prepare, Bind, Step,
On 29 Jun 2012, at 9:55pm, Jeff Archer jarch...@yahoo.com wrote:
Kevin Benson kevin.m.benson at gmail.com Fri Jun 29 16:32:55 EDT 2012
The mention of SQLITE_SCHEMA error and sqlite3VdbeExec() sounds like maybe
you're fighting an expired statement???
Not likely. I do Prepare, Bind, Step,
Pavel Ivanov paivanof at gmail.com Fri Jun 29 17:06:42 EDT 2012
Because SQLite successfully re-prepared this statement behind the
scenes and thus was able to successfully finish sqlite3_step()
function.
What could cause it to re-prepare the statement?
Is this something I need to find and fix?
Simon Slavin slavins at bigfraud.org Fri Jun 29 17:16:36 EDT 2012
Do you do the _prepare() first, then make a change to the database schema
? For instance
Start of app
Prepare the INSERT statement
CREATE TABLE
Bind the INSERT statement
Step the INSERT statement
No.
Create Table
Then in a
On 29 Jun 2012, at 10:27pm, Jeff Archer jarch...@yahoo.com wrote:
Pavel Ivanov paivanof at gmail.com Fri Jun 29 17:06:42 EDT 2012
Because SQLite successfully re-prepared this statement behind the
scenes and thus was able to successfully finish sqlite3_step()
function.
What could cause
On Fri, Jun 29, 2012 at 05:27:25PM -0400, Jeff Archer scratched on the wall:
Pavel Ivanov paivanof at gmail.com Fri Jun 29 17:06:42 EDT 2012
Because SQLite successfully re-prepared this statement behind the
scenes and thus was able to successfully finish sqlite3_step()
function.
What
On 29 Jun 2012, at 10:16pm, Simon Slavin slav...@bigfraud.org wrote:
Not likely. I do Prepare, Bind, Step, Finalize using a wrapper function.
The database file was created only moments before.
I'm sorry. I should have realised this was a FAQ:
http://www.sqlite.org/faq.html#q15
Simon.
On Fri, Jun 29, 2012 at 2:48 PM, Richard Hipp d...@sqlite.org wrote:
On Fri, Jun 29, 2012 at 3:40 PM, Nico Williams n...@cryptonector.com
wrote:
So, if I understand section 3.2 of the SQLite4 design page then it
will often be the case that lookup keys will not be stored in an order
that
On Fri, Jun 29, 2012 at 4:39 PM, Cory Nelson phro...@gmail.com wrote:
On Fri, Jun 29, 2012 at 2:48 PM, Richard Hipp d...@sqlite.org wrote:
What is the rationale for the 7-bit BINARY encoding? The performance impact
will surely outweigh any convenience of being able to treat blobs as
On Fri, Jun 29, 2012 at 6:09 PM, Nico Williams n...@cryptonector.comwrote:
On Fri, Jun 29, 2012 at 4:39 PM, Cory Nelson phro...@gmail.com wrote:
On Fri, Jun 29, 2012 at 2:48 PM, Richard Hipp d...@sqlite.org wrote:
What is the rationale for the 7-bit BINARY encoding? The performance
impact
On Fri, Jun 29, 2012 at 5:24 PM, Richard Hipp d...@sqlite.org wrote:
varint+value does not sort BLOBs in lexicographical order.
Not having a distinct terminator for the BLOB means that two BLOBs where
one is a prefix of the other might not compare correctly.
Would 31-bit encoding help?
On Fri, Jun 29, 2012 at 6:40 PM, Nico Williams n...@cryptonector.comwrote:
On Fri, Jun 29, 2012 at 5:24 PM, Richard Hipp d...@sqlite.org wrote:
varint+value does not sort BLOBs in lexicographical order.
Not having a distinct terminator for the BLOB means that two BLOBs where
one is a
OK, I give :)
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Hello, We use SQLite C/C++ API interface. We are in the process of migrating
our product (a C/C++ application) from 32 bit to 64 bit. We build our own
SQLite library with SQLite source code. Question:Should we continue building
it as a 32 bit library, and link it with 64 bit product, or
On Sat, Jun 30, 2012 at 1:56 AM, Pam Li pam...@hotmail.com wrote:
Hello, We use SQLite C/C++ API interface. We are in the process of
migrating our product (a C/C++ application) from 32 bit to 64 bit. We
build our own SQLite library with SQLite source code. Question:Should we
continue
Never heard about tunnelling before this, but I tried to turn it off and
it has no effect. I've also (numerously) deleted the whole folder and
created it from scratch and I'd still get that contents. Interestingly,
I now keep getting a different contents than before - it's now from the
last
Could it be that the .ext is used by the OS or other apps with some caching
scheme? Try different extension...
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/06/12 16:56, Pam Li wrote:
Question:Should we continue building it as a 32 bit library, and link
it with 64 bit product
It is virtually impossible to link a 32 bit library into a 64 bit product.
As an example a 64 bit pointer can't be passed
Regarding:
Could it be that the .ext is used by the OS or other apps with some
caching scheme?
Well, this symptom is so amazingly strange, it undeniably belongs in the
Ext Files.
(To those outside the U.S -- this is just a joke on
http://en.wikipedia.org/wiki/The_X-Files
)
Hi,
I'm trying to provide a not-really-spatialite toolset for C# users (since they
often seem to have trouble with spatialite / extension loading).
No problem with SELECT from an existing database / table. However I'd like to
provide the capability to perform an INSERT of a newly created
On 30/06/2012 10:32 AM, Donald Griggs wrote:
Regarding:
Could it be that the .ext is used by the OS or other apps with some
caching scheme?
Well, this symptom is so amazingly strange, it undeniably belongs in the
Ext Files.
(To those outside the U.S -- this is just a joke on
Thanks very much, Stephen and Roger, for your time and help.
pam
Date: Fri, 29 Jun 2012 17:31:21 -0700
From: rog...@rogerbinns.com
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] SQLITE 64bit Application Support?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/06/12 16:56,
On Sat, 30 Jun 2012 00:54:44 +1000, Dennis Volodomanov
i...@psunrise.com wrote:
On 30/06/2012 12:19 AM, Black, Michael (IS) wrote:
It persists across a reboot?
You can create a database, delete it, reboot, and your app will still
see the original table?
All I can say is wow...your system
Forgive me if I seem dense, but from
http://www.sqlite.org/src4/doc/trunk/www/index.wiki and elsewhere on sqlite.org,
though I can see individual source files, I don't see any place to get the whole
SQLite 4 source at once, either as a tarball or version control instructions.
So where do we go
83 matches
Mail list logo
