[sqlite] PRAGMA user_version;

2006-05-31 Thread Preston & Chrystie
If I have never set the user_version will the value always be 0? I plan to start using user_version in my app, I will need to set this value to a approprate value if it has not yet been set, and i am just double checking that it is always 0 untill i set it. Anybody have a better way to hold

Re: [sqlite] Encryption

2006-05-11 Thread Preston & Chrystie
te.org the last one is 3.3.5. What is the diference ? , where i can download encryption ( that it's a need funcionality for sqlite ) Thanks !!! On 5/10/06, Preston & Chrystie <[EMAIL PROTECTED]> wrote: > I'm having trouble compiling the 3.4.5 version with encryption > extensions.. I

Re: [sqlite] Possible bug with non-standard characters in column names

2006-05-11 Thread Preston &amp; Chrystie
if your first statement after creating the database is: PRAGMA encoding = "UTF-16"; then the error you get is slightly different: sqlite> ALTER TABLE test1 ADD straße VARCHAR(255); SQL error: malformed database schema - near "(": syntax error I was hoping that would fix it for you.. guess not,

[sqlite] sqlite error after upgrade to 3.3.5

2006-05-11 Thread Preston &amp; Chrystie
Hi all, I recently upgraded my project from 3.2.2 to 3.3.5 (or if you look at my last post 3.4.5 ;) and have found a situation where sqlite tries to access an invalid memory location in file vdbe.c line 3633 (pC==0). I have confirmed that this query causes the command line utility (pre-compiled

[sqlite] Encryption

2006-05-10 Thread Preston &amp; Chrystie
I'm having trouble compiling the 3.4.5 version with encryption extensions.. I have done it a hundred times before, but i just switched to a new computer and don't know what stupid mistake i am making... (NOTE: *.c is everything in the zip file with the addition of crypto3.c and exclusion of

[sqlite] column name inconsistency...

2005-08-12 Thread Preston &amp; Chrystie
I know there was a lot of talk about columns names a while back and i don't want to start it all up again, but i have noticed some things in the 3.2.2 release that seem a little odd to me. if i write a query as follows: select a.id, b.stuff from a inner join b on a.id=b.id; The column names