[sqlite] Question about sqlite3_extended_result_codes()

Hello, I have a couple questions about sqlite3_extended_result_codes(): 1) Once I enable it, is it possible to determine whether extended result codes is enabled for a given a sqlite3* handle? 2) Do I have to process each result code in order to obtain the "regular" SQLite code, or can I

Re: [sqlite] Feeds for sqlite releases

On Jun 27, 2009, at 6:49 PM, João Eiras wrote: > Hi ! > > I really missing having feeds to track sqlite releases. Currently I > either have to go through the mailing list, which is not low > traffic, or open the website. > Would you consider having an rss feed for sqlite releases ? There

Re: [sqlite] Feeds for sqlite releases

João Eiras wrote: > I really missing having feeds to track sqlite releases. Currently I > either have to go through the mailing list, which is not low traffic, > or open the website. Would you consider having an rss feed for sqlite > releases ? See if this helps:

Re: [sqlite] Feeds for sqlite releases

Hi, there already is an RSS feed - http://www.sqlite.org/cvstrac/timeline.rss - unfortunately it can't be limited to display only the milestones as regular web timeline can. Best regards, Filip Navara On Sun, Jun 28, 2009 at 12:49 AM, João Eiras wrote: > Hi ! > > I really

Re: [sqlite] first few characters of varchar() corrupted when SELECTing from a C++ program?

uralmaza...@pop3.ru wrote: > sqlite3_open_v2( "testdat", sqlDB, SQLITE_OPEN_READWRITE | > SQLITE_OPEN_CREATE, NULL ); > sqlite3_prepare_v2( sqlDB, "SELECT b FROM whee WHERE a='bing';", -1, > sqlStat, NULL ); > sqlite3_step( sqlStat ); > const unsigned char *testValue = sqlite3_column_text(

[sqlite] Feeds for sqlite releases

Hi ! I really missing having feeds to track sqlite releases. Currently I either have to go through the mailing list, which is not low traffic, or open the website. Would you consider having an rss feed for sqlite releases ? Thanks. ___ sqlite-users

[sqlite] first few characters of varchar( ) corrupted when SELECTing from a C++ p rogram?

Greetings, maybe it's just me being stupid, I'll best jump right to the code: sqlite3_open_v2( "testdat", sqlDB, SQLITE_OPEN_READWRITE | SQLITE_OPEN_CREATE, NULL ); sqlite3_prepare_v2( sqlDB, "SELECT b FROM whee WHERE a='bing';", -1, sqlStat, NULL ); sqlite3_step( sqlStat ); const unsigned

Re: [sqlite] very large SQLite tables

I have actually implemented such a structure, and it worked well. Kosenko Max wrote: > You're talking about db size much less than 1 billion records. > > In 1 billion records db with described scenario cache hit ratio so small > that everything you're talking about just very close to zero

[sqlite] SQLite version 3.6.16

SQLite version 3.6.16 is now available on the SQLite website: http://www.sqlite.org/ Version 3.6.16 is a regular monthly maintenance release. Curiously, even though it is released at the end of June, version 3.6.16 is considered the monthly maintenance release for July. We have

Re: [sqlite] New-B

THANKS MAN! On Sat, Jun 27, 2009 at 10:14 AM, P Kishor wrote: > On Sat, Jun 27, 2009 at 10:03 AM, Jamiil Abd Al Qadir > wrote: > > Hey kids! > > I wanted to know if there is a tutorial of how to create new database > > tables, sort tables, etc., etc. > >

Re: [sqlite] unable to write the string "1.0" into a database table

I am really sorry, The correct code is given below: // #include #include #include #include #include const char *create_and_insert = "create table some_tbl (id int primary key, version text check (version in

Re: [sqlite] New-B

On Sat, Jun 27, 2009 at 10:03 AM, Jamiil Abd Al Qadir wrote: > Hey kids! > I wanted to know if there is a tutorial of how to create new database > tables, sort tables, etc., etc. > .. Its called Google. It opens doors to all kinds of tutorials. You can also try your luck with

[sqlite] New-B

Hey kids! I wanted to know if there is a tutorial of how to create new database tables, sort tables, etc., etc. TIA -- Happiness has many doors, and when one of them closes another opens, yet we spent so much time looking at the one that is shut that we don't see the one that just opened..

Re: [sqlite] very large SQLite tables

You're talking about db size much less than 1 billion records. In 1 billion records db with described scenario cache hit ratio so small that everything you're talking about just very close to zero difference in effect. Because 1 uncached random IO operation is 10ms. Any reasonable calculations

Re: [sqlite] unable to write the string "1.0" into a database table

On 27 Jun 2009, at 8:47am, chandan wrote: > const char *create_and_insert = "create table some_tbl (id int primary > key, version text check (version in (\"1.0\")));" >"insert into some_tbl (id) values (1);"; > const char *update_sql = "update some_tbl set version = ? where id > = ?"; I

Re: [sqlite] How to find the version of the database.

On 27/06/2009 3:36 AM, Kalyani Phadke wrote: > Is there any way to find the version of SQlite3 database. eg. I have > test.DB file . I want to know which SQLite3 version its using ..eg 3.5.4 > or 3.6.15? Short answer: You can't know. What problem do you face that makes you want to know? If the

Re: [sqlite] very large SQLite tables

Quite wrong. Searching a B-Tree is relatively inexpensive but node splits are expensive. Inserting a non-terminal key in a part filled leaf node is cheap, inserting a terminal key is more expensive and a split is more expensive again The reason we spend the extra resources maintaining

Re: [sqlite] very large SQLite tables

Expenses in B-Tree not in the node splitting (that is really not that often and takes small amount of time). As I've said - it's in finding right place to insert. Root level which takes 1 page will do the same as your hash index. And will use much less space in cache. This root page in such DB

Re: [sqlite] unable to write the string "1.0" into a database table

On Jun 27, 2009, at 2:47 PM, chandan wrote: > The code snippet is shown below: > > / > **/ > #include > #include > #include > #include > #include > > const char *create_and_insert = "create

Re: [sqlite] very large SQLite tables

This technique is used extensively in disk cacheing and in maintaining file directories with huge numbers of files.. I would expect it toincrease key insertion speed because it removes a level of index in the B-tree of each index. The expensive activity in a B-tree index insertion is a node

Re: [sqlite] unable to write the string "1.0" into a database table

The code snippet is shown below: /**/ #include #include #include #include #include const char *create_and_insert = "create table some_tbl (id int primary key, version text check (version in

Re: [sqlite] unable to write the string "1.0" into a database table

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 chandan wrote: >I have attached the C program along this mail. This mailing list strips all attachments, so we can't see your code :-) > Am i doing anything wrong in the program? Yes. SQLite does fundamentally work. We'd have noticed by now

[sqlite] unable to write the string "1.0" into a database table

Hi, I have attached the C program along this mail. The program does the following: 1. Open a database file (Indicated by the argv[1] argument). 2. Create the table "some_tbl" and insert a row into the table. 3. Update the second column of the new row to value "1.0". 4. Close the