[sqlite] How sqlite3_bind_parameter_count counts binding parameters

2006-05-02 Thread Aidan Reel
Hi Using 3.3.5 if you prepare the following statement 'insert into Table (id, id1) values( ?3, :id ); ' and then use sqlite_bind_parameter on the prepared statement you will receive the number 4. I appreciate where that answer is coming from, it takes the largest unnamed argument and adds

[sqlite] Creating 3.3.5 dylib on OSX 10.4

2006-04-27 Thread Aidan Reel
Hi I have followed the normal steps mkdir bld cd bld ../configure make there are no messages suggesting that any errors occurred in the .libs folder I see dylib files but they are all over 1MB, where as the binary in /usr/lib or from the starkit on www.sqlite.org are around 320Kb. When

[sqlite] Libraries supplied via the starKit

2006-04-25 Thread Aidan Reel
Hi I am running 3.3.5 on OSX10.4 from the starKit available on www.sqlite.org. I have written a wrapper and I am now unit testing each of the C functions. I am getting fails on sqlite3_table_column_metadata sqlite3_release_memory sqlite3_soft_heap_limit Could these be due to the

[sqlite] Using sqlite3_complete

2006-04-25 Thread Aidan Reel
Hi If I give sqlite3_complete the string 'select from Person;' should I expect it to return zero or one? Since it is not a valid Select statement I am expecting a zero, instead I get a one. If I remove the semicolon from the end of the string I receive a zero. Regards Aidan

[sqlite] PRAGMA case_sensitive_like

2006-01-31 Thread Aidan Reel
Hi I am writing a wrapper around version 3.2.8 taken from the starkit , I have implemented and unit tested execution of queries and commands. I am now providing methods for the various PRAGMAs. I have implemented and successfully unit tested PRAGMAs such as auto_vacuum and count_changes. I

[sqlite] sqlite3_column_blob(...) and finalize

2005-06-24 Thread Aidan Reel
Hi I have a select statement that returns some BLOBs. When I finalize the select statement, the memory pointed to by the pointer returned by const void * sqlite3_column_blob(...) is cleared. Is this the expected behaviour? What should I do in order to obtain a pointer to memory that is