[sqlite] SQLite 3 release
Hello, Dr. Hipp, please, what is the time estimate for releasing the version 3? I believe that it's not only me looking forward to it! It is too lovely, the version 3, how long should I live with version 2? :-)) Jakub
Re: [sqlite] SQLITE_ERROR instead of SQLITE_FULL
George Ionescu wrote: > > So, my question is this: if sqlite cannot insert data into the database > because it doesn't have enough free space, shouldn't it return SQLITE_FULL > insted of SQLITE_ERROR ? > Did you write a ticket? -- D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
Re: [sqlite] SQLite 3 release
Jakub Adamek wrote: Hello, Dr. Hipp, please, what is the time estimate for releasing the version 3? I believe that it's not only me looking forward to it! It is too lovely, the version 3, how long should I live with version 2? :-)) I had hoped to do a release this week. But there are some errors in the regression suite at the moment and I'm too busy with other crises to fix them. I'll be travelling all next week. Surely by the end of the month -- D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
[sqlite] Thank you
Hello, I'm just passing by to say a big fat "thank you" to the SQLite developers. We actually managed to compile SQLite for an Intermec ck1 barcode scanner/mobile computer (running ucLinux). It required some hacking around as we were not able to get the configure script to run properly, but in the end it worked (with help of the patch here http://www.menie.org/georges/DragonEngine/sqlite.html). What's most amazing is the incedible speed of SQLite. The scanner is powered by a 66 Mhz ARM CPU by Samsung and still, SQLite stays fast: Searching for a particular scanned barcode in a table containing ~1 entries is done instantly in much less then half a second. This fast speed, combined with the really small code size and the impressive feature set is extremely great. Many thanks to the developers! Philip PS: Is there some way to donate something to the team? I unfortunately will not be able to contribute much code-wise, so I think, a donation is the least thing I can do.
[sqlite] sqlite 3.0 without 64 bit ints
Hi, Has anyone tried or succeeded in building SQLite 3.0 with a compiler that doesn't support 64 bit integers? Alternatively, does anyone know what won't work with a version built with 32 bit ints only? The databases we use are not so big that they need 64 bit keys etc. We are satisfied with the 32 bit int values used in version 2, and one of the compilers we use doesn't support 64 bit ints. My idea is to modify the definitions of sqlite_int64 and sqlite_uint64 to use long and unsigned long in sqlite3.h then build a custom library. I understand that this may not be compatible with third party sqlite3 tools. I currently get a couple of warnings regarding some hardcoded 64 bit constants in vdbe.c and vdbeaux.c. Also there are some asserts in btree.c that check the size of i64 and u64 that will fail with DEBUG defined. There are functions that check if a given string of digits can be converted to fit in a 64 bit value that will have to change. Preliminary testing of this custom version seems to work. I get warnings when building the test suite, but it runs through most of the tests (including the bigfile tests). The testfixture dies for btree-1.6, capi3-8.2 and I get failures several other tests (show below) that all appear to be directly related to numbers bigger than 32 bits. Failures on these tests: bind-3.1 bind-3.2 bind-4.1 func-11.1 misc1-9.1 misc2-4.1 misc2-4.2 misc2-4.3 misc2-4.4 misc2-4.5 misc2-4.6 misc3-3.6 misc3-3.7 misc3-3.8 misc3-3.9 misc3-3.10 misc3-3.11 misc3-3.12 misc3-3.13 misc3-3.14 pager-2.3.6 pager2-2.3.6 printf-8.3 printf-8.4 printf-8.5 rowid-7.7 rowid-12.2 types-2.1.8 types-2.1.9 Does anyone know of any gotcha's I should expect? TIA Dennis Cote
[sqlite] What does the first expr do in a CASE statement ?
What does the first expr do in a CASE expression ? I understand the rest of the syntax, but I don't get what the very first expr (after the keyword "case") does.. And I couldn't find the answer in the documentation or wiki.. Thanks Randall Fox
Re: [sqlite] What does the first expr do in a CASE statement ?
Randall Fox wrote: What does the first expr do in a CASE expression ? I understand the rest of the syntax, but I don't get what the very first expr (after the keyword "case") does.. And I couldn't find the answer in the documentation or wiki.. Thanks Randall Fox There's a few ways you can use case statements, I think you're referring to this: select case field1 when 1 then field1+1 when 2 then field1/2 else 1 end as casefield from table1; in which case, field1 will be compared to each "when value" to determine which "then value" to return. It's very similar to a switch statement. Case can also be used as an if elseif else type statement, when the field is omitted. select case when field1 is null then field2 else field1 end as casefield from table1; John LeSueur
Re: [sqlite] What does the first expr do in a CASE statement ?
On Fri, 17 Sep 2004 19:49:34 -0600, you wrote: >Randall Fox wrote: > >>What does the first expr do in a CASE expression ? >> >>I understand the rest of the syntax, but I don't get what the very >>first expr (after the keyword "case") does.. And I couldn't find the >>answer in the documentation or wiki.. >> >>Thanks >> >>Randall Fox >> >> >There's a few ways you can use case statements, I think you're referring >to this: > >select >case field1 > when 1 then > field1+1 > when 2 then > field1/2 > else > 1 >end as casefield >from table1; > >in which case, field1 will be compared to each "when value" to determine >which "then value" to return. It's very similar to a switch statement. > >Case can also be used as an if elseif else type statement, when the >field is omitted. > > >select >case > when field1 is null then > field2 > else > field1 >end as casefield >from table1; > > >John LeSueur Thanks.. So it is a true SWITCH.. I didn't realize you can have multiple when statements!! wow! Thanks Randall Fox
