[sqlite] ANN: SQLite 3.6.16.C#

I am pleased to announce that the C# port is done to the point where others can look at it. The project is located at http://code.google.com/p/sqlitecs Enjoy, Noah Hart -- View this message in context: http://www.nabble.com/ANN%3A--SQLite-3.6.16.C--tp24764742p24764742.html Sent from the

Re: [sqlite] Reasons for SQLITE_BUSY

--- nikol...@rath.org wrote: > "Edzard Pasma" writes: >> --- nikol...@rath.org wrote: >>> "Igor Tandetnik" writes: Nikolaus Rath wrote: > I am accessing the same database from different threads. Each > thread > has

Re: [sqlite] Foreign Key constraint checking

On 31 Jul 2009, at 8:25pm, Shaun Seckman (Firaxis) wrote: > I am well aware that SQLite doesn't enforce FK's and that a way around > this is to use triggers. This lack of enforcing actually has worked > to > my advantage as when populating my database I can insert data out of > order.

Re: [sqlite] Foreign Key constraint checking

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shaun Seckman (Firaxis) wrote: > I am well aware that SQLite doesn't enforce FK's and that a way around > this is to use triggers. Hopefully you are also aware of the genfkey functionality in the shell which lets you automate generation of those

[sqlite] Foreign Key constraint checking

Hello, I am well aware that SQLite doesn't enforce FK's and that a way around this is to use triggers. This lack of enforcing actually has worked to my advantage as when populating my database I can insert data out of order. However, after all data has been inserted into the database, I'd

Re: [sqlite] Reasons for SQLITE_BUSY

"Edzard Pasma" writes: > --- nikol...@rath.org wrote: >> "Igor Tandetnik" writes: >>> Nikolaus Rath wrote: I am accessing the same database from different threads. Each thread has its own connection. I have set the

Re: [sqlite] Multi-master replication with updated Ver sioning extension

Hello! On Thursday 30 July 2009 18:17:45 Jim Showalter wrote: > MD5 hashes can still collide. How does this implementation deal with > hash collisions? Now it is possible to use any hash function: -- first column is unique key select versioning('arg1','sessions'); -- use md5 hash of all fields

Re: [sqlite] Multi-master replication with updated Versioning extension

Hello! On Friday 31 July 2009 18:34:17 Ken wrote: > I've looked at your code and discussions on this list about the versioning. I > have a few questions. > > 1. How are you moving the data around from one master to another? > 2. How are you applying the changes once moved to the master? By the

Re: [sqlite] stupid me -> corrupted db file

On 30 Jul 2009, at 3:31pm, Rudi Fay wrote: > I tried "pragma integrity_check;" with the result "SQL error: database > disk image is malformed" But that may not stop you from rescuing (the majority of ?) the data. The error may be in an index or something else that isn't used when you just

Re: [sqlite] SQL error: database disk image is malformed - other possibility than dump/load

On Jul 31, 2009, at 12:00 AM, rupert.thurner wrote: > is there another possibility but exporting and importing the data to > get rid of: > SQL error: database disk image is malformed > ? > > here the details of the error and the commands we used. but we are not > sure why exporting works and

Re: [sqlite] Multi-master replication with updated Versioning extension

Alex, I've looked at your code and discussions on this list about the versioning. I have a few questions. 1. How are you moving the data around from one master to another? 2. How are you applying the changes once moved to the master? --- On Fri, 7/31/09, Alexey Pechnikov

Re: [sqlite] SELECT DISTINCT bug in SQLite 3.6.0?

... or might it even be so, that good praxis is when using field names, to always use the AS clause, even if no table-alias are used? Like: rs=db.SQLSelect("SELECT x AS x FROM t") zstring=rs.Field("x").StringValue Lennart Ramberg On Fri, Jul 31, 2009 at 3:12 PM, Lennart

Re: [sqlite] Multi-master replication with updated Versioning extension

Hello! I made some changes: hash field in actions table has always name "checksum" (so versioning and replication logic doesn't influence of hash algorithm) versioning() function without second argument now start "local" mode history and actions tables are renamed

Re: [sqlite] SELECT DISTINCT bug in SQLite 3.6.0?

Thanks for quick responses, Actually, removing DISTINCT removes the problem, but anyway, as I understand, I should always use the AS clause when using alias to be on the safe side, right? Lennart Ramberg On Fri, Jul 31, 2009 at 2:40 PM, Igor Tandetnik wrote: > Lennart

Re: [sqlite] SELECT DISTINCT bug in SQLite 3.6.0?

Lennart Ramberg wrote: > dim rs as RecordSet > rs=dbEta.SQLSelect("SELECT DISTINCT V.resanr,C.namn"_ > +" FROM Voyages V,Category C WHERE C.kategorinr=V.kategorinr") > > dim namnstr as string > > namnstr=rs.Field("namn").StringValue 'I get a NilObjectException > here in 3.6.0 ... >

Re: [sqlite] SELECT DISTINCT bug in SQLite 3.6.0?

On Fri, 31 Jul 2009, Lennart Ramberg might have said: > Hello, > > I'm new to this list and what prompted me to sign up was a SELECT > DISTINCT problem I experience in REALbasic (Linux), which has SQLite > built-in. > > REALbasic downgraded their latest version from SQLIte 3.6.3 to 3.6.0 > Now,

[sqlite] SELECT DISTINCT bug in SQLite 3.6.0?

Hello, I'm new to this list and what prompted me to sign up was a SELECT DISTINCT problem I experience in REALbasic (Linux), which has SQLite built-in. REALbasic downgraded their latest version from SQLIte 3.6.3 to 3.6.0 Now, 3.6.0 behaves differently than 3.3.6 and 3.6.3 in the following

[sqlite] SQL error: database disk image is malformed - other possibility than dump/load

is there another possibility but exporting and importing the data to get rid of: SQL error: database disk image is malformed ? here the details of the error and the commands we used. but we are not sure why exporting works and vacuum should not work. we used sqlite 3.6.10, solaris. # sqlite3

[sqlite] stupid me -> corrupted db file

Hey there, i have just done a stupid thing - messing with the main db file without a backup. I was "modifying" the db file with an hex-editor (done before), unfortunately this time something went wrong and the db file became corrupted. I tried "pragma integrity_check;" with the result "SQL error:

Re: [sqlite] Looking for a w_char alternative to the sqlite3_mprintf famili of functions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 a...@zator.com wrote: > I need verify that the "bind" method does not have problems with that kind of > strings. The method to bind a string has no problem with any kind of string. Behind the scenes it does not convert what you supply into some

Re: [sqlite] Looking for a w_char alternative to the sqlite3_mprintf famili of functions

Roger: Thanks for your input. Really already I was using the suggested functions, but for some reason, the sections with strings where user inputs can be adds single quotes, have maintained that legacy code. Any way thanks again,althought I need verify that the "bind" method does not have