Re: [sqlite] ISO-8601 date string and '>' comparison buggy

2013-08-28 Thread Thomas Jarosch
Zitat von Igor Tandetnik : SQLite doesn't have "datetime" data type. All these values are plain strings, and are compared as such. It just so happens that, if you use a suitable format consistently, usual string comparisons also order dates and times correctly. So, don't mix and match th

[sqlite] ISO-8601 date string and '>' comparison buggy

2013-08-28 Thread Thomas Jarosch
Hi, consider this stripped-down database: -- CREATE TABLE "horde_alarms" ("id" INTEGER PRIMARY KEY, "alarm_end" datetime); INSERT INTO "horde_alarms" VALUES(1, '2013-08-28 22:00:00'); -- These queries work fine: -- sqlite> SELECT * FROM horde_alar

[sqlite] [PATCH 2/2] Fix file descriptor leak on error

2011-08-27 Thread Thomas Jarosch
ert act of relinquishment in perpetuity of all present and future rights to this code under copyright law. Signed-off-by: Thomas Jarosch --- tool/lemon.c |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/tool/lemon.c b/tool/lemon.c index bd2938b..1f8082c 100644 --- a/to

[sqlite] [PATCH 1/2] Fix memory corruption in test routine

2011-08-27 Thread Thomas Jarosch
ert act of relinquishment in perpetuity of all present and future rights to this code under copyright law. Signed-off-by: Thomas Jarosch --- src/test1.c |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/src/test1.c b/src/test1.c index 7fdf54b..2045c81 100644 --- a/src/tes

Re: [sqlite] .dump and transactions

2009-01-20 Thread Thomas Jarosch
On Monday, 12. January 2009 14:20:40 Thomas Jarosch wrote: > If an open transaction would block the dump of the database, > then the second command line tool should busy wait until a timeout occurs > or atleast return an error message. I finally tracked this down by testing sqlite 3.6

Re: [sqlite] .dump and transactions

2009-01-12 Thread Thomas Jarosch
On Monday, 12. January 2009 13:52:47 P Kishor wrote: > > Here's a short example to reproduce the problem: > > > > sqlite3 test.db > > create table test (name varchar(16)); > > begin transaction; > > insert into test values ('test'); > > did you forget to COMMIT here? Thanks for your reply. In fact

Re: [sqlite] .dump and transactions

2009-01-12 Thread Thomas Jarosch
On Friday, 9. January 2009 10:34:32 Thomas Jarosch wrote: > I run a small script every night via cron to backup a database > using the ".dump" statement. SQlite version is 3.6.6.2 on Linux. > > Normally this script works fine and from time to time > I get a backup

[sqlite] .dump and transactions

2009-01-09 Thread Thomas Jarosch
Hello together, I run a small script every night via cron to backup a database using the ".dump" statement. SQlite version is 3.6.6.2 on Linux. Normally this script works fine and from time to time I get a backup file that looks like this: --- BEGIN TRANSACTION; END TRANSACTION; -