Re: [sqlite] Upcoming Conferences

[EMAIL PROTECTED] wrote: Dan Kennedy <[EMAIL PROTECTED]> wrote: Yes. I appologize for the misspelling. And, No, I was not aware of the second Frankfurt. Frankfurt am Main is the only one I had ever heard of. How about "Sidney" then? We're offended too! :) If you haven't

Re: [sqlite] International Language Support

Hi Dan, I think we need to know this here: How do your SELECT statements look like? What's the keyword your international clients use - to find what data? And what's the data in the table? What might be already a help is: " The LIKE operator is not case sensitive and will match upper case

Re: [sqlite] Multi-threading.

Mrs. Brisby wrote: On Sat, 2005-07-30 at 14:30 +0200, Jan-Eric Duden wrote: Win9X doesn't support the API async file operations. WinNT/2K/XP does support it. It supports everything it needs to: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base

Re: [sqlite] SQLITE_SCHEMA and statement parameters

Vladimir Vukicevic wrote: On 4/21/05, D. Richard Hipp <[EMAIL PROTECTED]> wrote: How about sqlite3_transfer_bindings(). So if you get an SQLITE_SCHEMA error you rerun sqlite3_prepare() to get a new sqlite3_stmt, then call sqlite3_transfer_bindings() to transfer bindings from the old statement

Re: [sqlite] Storing 64-Bit Addresses

How about storing the 64 bit integers as binaries and write user functions (using sqlite3_create_function ) to do the computation and comparison? William Hachfeld wrote: On Thu, Mar 31, 2005 at 01:52:53PM -0800, Ted Unangst wrote: Store the length of the region, instead of the end. Or is

Re: [sqlite] nested transactions?

Kervin L. Pierre wrote: Hello again, Are there plans for supporting nested transactions in the future? Would that be a difficult extension to code ( eg. if one thought they could give it a try :) ) The current restriction makes it hard to use SQLite in developing a API eg exposed_func1() {

Re: [sqlite] Proposal: limit the number of columns in a table to 2000.

How about a constant that can be changed at compile time? D. Richard Hipp wrote: As currently implemented, there is no fixed limit to the number of columns you can put in a table in SQLite. If the CREATE TABLE statement will fit in memory, then SQLite will accept it. Call the number of columns

[sqlite] sqlite3 statements and database changes

Hi! I figured out a while ago, that prepared statements (sqlite3_prepare/sqlite3_prepare16) will get invalid if database scheme changes. That happens also to statements that don't depend on the changed objects. Unfortunately, sqlite3_step only returns SQLITE_ERROR in this case. This is

Re: [sqlite] getting rid of dirty SQLITE_BUSY workaround

The issue 1159 was marked as "not_a_bug". So is there a misunderstanding? Thomas Lotterer wrote: I've created an application that makes use of SQLite3. Occasionally, multiple instances of that application run at the same time and need to write to the database simultaneously. When I decided to use

[sqlite] COLLATE and GROUP BY

lumn "colA" with COLLATE NOCASE. "CREATE TABLE t (colA TEXT COLLATE NOCASE);" Thanks a lot, Jan-Eric Duden

[sqlite] sqlite3_reset

! Jan-Eric Duden