Re: [sqlite] How to determine db file version?

At 7:53 PM -0400 8/29/04, D. Richard Hipp wrote: Marco Bambini wrote: It is safe to read the first N bytes in a db file and check for the string "** This file contains an SQLite 2..." or the string "** This file contains an SQLite 3..." to determine if the db was created with the 2.x or 3.x

Re: [sqlite] How to determine db file version?

> It is safe to read the first N bytes in a db file ... ? Yes. As far as I know, that's the only sure way to determine the version. Unfortunately, the form of the header changed in version 3, but if you read the first 33 bytes, you'll have an array that you can search for "SQLite 2" or "SQLite

[sqlite] How to determine db file version?

It is safe to read the first N bytes in a db file and check for the string "** This file contains an SQLite 2..." or the string "** This file contains an SQLite 3..." to determine if the db was created with the 2.x or 3.x version? Is there a better method? Thanks. Marco Bambini SQLabs.net

Re: [sqlite] Strange sorting behaviour

Paolo Vernazza wrote: I found a strange behaviour when ordering a table where a row is defined with COLLATE NOCASE and the data contains empty strings. ... the result is a| a|a b|a b| a|b b|b It is a feature or a bug? A bug in NOCASE. --- main.c 28 Aug 2004 16:19:01 - 1.255 +++

[sqlite] Strange sorting behaviour

I found a strange behaviour when ordering a table where a row is defined with COLLATE NOCASE and the data contains empty strings. Create a table like this: CREATE TABLE test (col_a TEXT COLLATE NOCASE, col_b TEXT COLLATE NOCASE); INSERT INTO test (col_a, col_b) VALUES ('a', ''); INSERT INTO

[sqlite] Version 3.0.5 (beta)

SQLite version 3.0.5 (beta) is now available on the website. -- D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565