RE: [sqlite] filename limit in sqlite_open

> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > "Shields, Daniel" <[EMAIL PROTECTED]> wrote: > > Does anyone know the maximum length of the filename passed to > > sqlite_open. We seem to see truncation on long file names (> 32 > > chars?)

[sqlite] filename limit in sqlite_open

Does anyone know the maximum length of the filename passed to sqlite_open. We seem to see truncation on long file names (> 32 chars?) Thanks, Daniel. == Please access the attached hyperlink for an important electronic

RE: RE: [sqlite] How long can I keep a prepared statement around?

> Looking at the implementation of sqlite3_expired, its just a > comparison of the expired flag in the statement or if the > passed statement is NULL. The cost is an additional if > statement before execution, however this does not save you > from SQLITE_SCHEMA errors. In theory someone could

RE: [sqlite] How long can I keep a prepared statement around?

> > Use the function sqlite3_expired to determine, when you need > to recompile a prepared statement. That's the approach I use. > > Mike How does this compare with the re-preparing statements that have failed with a SQLITE_SCHEMA error during sqlite3_step? e.g.

RE: [sqlite] SQLiteSpy vs. SQLite.dll speed comparison

> Daniel: > Thanks for the suggestion. > I wasn't aware that the prepare statement gained you that > much for one-table select queries. > I use it for multi-100k inserts (along with trans.) and it > saves quite a bit of time. > This is my sql for the present problem: > > select * from (select

RE: [sqlite] SQLiteSpy vs. SQLite.dll speed comparison

> I've been using the SQLiteSpy sql browser tool from Ralf > Junker at The Delphi Inspiration to test and time sql. > Unfortunately for my assumptions, it appears that SQLiteSpy > runs queries about 2.5x faster than using the SQLite dll in my code. > Does anyone know how to speed up SQLite

RE: [sqlite] RE: Problem executing sqlite3_prepare command

> Never mind. I just realized (from rereading a previous newsgroup > posting) that the wildcards can only be used to replace values within > expressions (and not the table or column names). > > I use printf for these cases before preparing: sprintf(buf, "INSERT INTO %s VALUES (?,

[sqlite] sqlite schema error

I apologise in advance as this topic has been done to death. Can I assume that a schema error can only occur when calling sqlite3_step? I've trawled through the documentation but cant find a definitive answer. Thanks, Daniel. -- Daniel Shields Equities IT +44(0)207 888 9248 [EMAIL

RE: [sqlite] weird parser crash

> If you would just submit the particular query that is causing > the problem, that would be an enormous help. If you can also > include the schema for your database, so much the better. Statement failing in sqlite3_prepare is: "UPDATE SDDSTORE SET SDD = ?, TIMESTAMP =

RE: [sqlite] weird parser crash

> You are, it seems, the person who posted ticket #1557. > > A stack trace is of little to no help in fixing a problem > like this. What is needed is a script that when feed into > the "sqlite" command-line shell will reproduce the problem. > Send in such a script (or added it to ticket #1557)

[sqlite] weird parser crash

I have a process that consistently crashes preparing a fairly innocuous statement. Has anyone seen anything similar? Any suggestions for a fix/workaround? The stack trace of the problem follows. Thanks, Daniel. [EMAIL PROTECTED] ([EMAIL PROTECTED]) terminated by signal SEGV (no