Re: [Bacula-devel] SQLite3

2010-12-08 Thread Kern Sibbald
Hello Jason, On Wednesday 08 December 2010 15:54:07 Jason A. Kates wrote: > At this point I would suggest that it doesn't make sense for Bacula to > maintain support for sqlite with the next major release of Bacula. > > As you know scripts shipped with Bacula exist to move from sqlite to an > ent

Re: [Bacula-devel] SQLite3

2010-12-08 Thread Jason A. Kates
At this point I would suggest that it doesn't make sense for Bacula to maintain support for sqlite with the next major release of Bacula. As you know scripts shipped with Bacula exist to move from sqlite to an enterprise DB: bacula-sqlite_2_mysqldump.sh sqlite2pgsql With Bacula being as stable a

[Bacula-devel] SQLite3

2010-12-08 Thread Kern Sibbald
On Wednesday 08 December 2010 08:42:50 Joshua J. Kugler wrote: > On Sunday 28 November 2010, Kern Sibbald elucidated thus: > > On Sunday 28 November 2010 15:01:07 Dan Langille wrote: > > > Does this help? It arrived this morning from my inbox > > > > I see quite a few dumps like this one -- basica

Re: [Bacula-devel] sqlite3 create error with latest git

2010-04-16 Thread Kern Sibbald
Thanks. I have fixed it. Kern On Friday 16 April 2010 06:11:42 Craig Ringer wrote: > $ /home/craig/bacula-git/etc/create_sqlite3_database > > $ /home/craig/bacula-git/etc/make_sqlite3_tables > SQL error near line 41: near "INDEX": syntax error > SQL error near line 55: no such table: main.Restor

[Bacula-devel] sqlite3 create error with latest git

2010-04-15 Thread Craig Ringer
$ /home/craig/bacula-git/etc/create_sqlite3_database $ /home/craig/bacula-git/etc/make_sqlite3_tables SQL error near line 41: near "INDEX": syntax error SQL error near line 55: no such table: main.RestoreObject $ apt-cache policy sqlite3 sqlite3: Installed: 3.6.16-1ubuntu1 Candidate: 3.6.16-1

Re: [Bacula-devel] Sqlite3 and autoincrement

2009-08-24 Thread Kern Sibbald
On Monday 24 August 2009 15:05:43 Sven Hartge wrote: > Sven Hartge wrote: > > Kern Sibbald wrote: > >> Based on the information you provided below, I have reopened the bug > >> report and posted my suggested fix. Sorry that I missed the fact that > >> the Bacula developers added the offending "AUT

Re: [Bacula-devel] Sqlite3 and autoincrement

2009-08-24 Thread Sven Hartge
Sven Hartge wrote: > Kern Sibbald wrote: > >> Based on the information you provided below, I have reopened the bug report >> and posted my suggested fix. Sorry that I missed the fact that the Bacula >> developers added the offending "AUTOINCREMENT". I would appreciate a >> confirmation to the

Re: [Bacula-devel] Sqlite3 and autoincrement

2009-08-23 Thread Sven Hartge
Kern Sibbald wrote: > Based on the information you provided below, I have reopened the bug report > and posted my suggested fix. Sorry that I missed the fact that the Bacula > developers added the offending "AUTOINCREMENT". I would appreciate a > confirmation to the bug report whether or not

Re: [Bacula-devel] Sqlite3 and autoincrement

2009-08-22 Thread Kern Sibbald
Hello John, Based on the information you provided below, I have reopened the bug report and posted my suggested fix. Sorry that I missed the fact that the Bacula developers added the offending "AUTOINCREMENT". I would appreciate a confirmation to the bug report whether or not my suggested fix

[Bacula-devel] Sqlite3 and autoincrement

2009-08-21 Thread John Goerzen
Hi folks, I'm trying to troubleshoot a problem reported by a Debian user converting Bacula from Sqlite2 to Sqlite3. The problem is that when you dump a Bacula database from Sqlite2 and try to load it into Sqlite3, Sqlite3 crashes because there are fields marked AUTOINCREMENT. Kern has stated in h