Re: [sqlite] SQLiteSpy 1.5.4 released

2006-06-21 Thread Ralf Junker
Hello C.Peachment, >It appears that VACUUM is not the only SQL command to cause >this behaviour. I had done a number of INSERT and UPDATE >commands before closing the database and attempting to use >it with PHP. The VACUUM command was not used. I am surprised to read this. I would be interested

Re: [sqlite] SQLiteSpy 1.5.4 released

2006-06-21 Thread C.Peachment
On Wed, 21 Jun 2006 09:24:35 +0200, Ralf Junker wrote: >>1. SQLiteSpy is able to read and work with database files >>formatted by versions of Sqlite earlier than 3.3.6 but it also >>appears to change the database format rather than leave >>it as it was found. >> >>I use php version 5.1.4

Re: [sqlite] SQLiteSpy 1.5.4 released

2006-06-21 Thread Ralf Junker
Hello C.Peachment, >1. SQLiteSpy is able to read and work with database files >formatted by versions of Sqlite earlier than 3.3.6 but it also >appears to change the database format rather than leave >it as it was found. > >I use php version 5.1.4 including Sqlite version 3.2.8. >There is a

Re: [sqlite] SQLiteSpy 1.5.4 released

2006-06-20 Thread C.Peachment
On Tue, 20 Jun 2006 15:34:21 +0200, Ralf Junker wrote: >SQLiteSpy 1.5.4 is released. Changes include: >* Updated to SQLite3 3.3.6. >* The schema tree view did not automatically reflect if a table was emptied or >initial records were being added. >* The default text encoding for newly

[sqlite] SQLiteSpy 1.5.4 released

2006-06-20 Thread Ralf Junker
SQLiteSpy 1.5.4 is released. Changes include: * Updated to SQLite3 3.3.6. * The schema tree view did not automatically reflect if a table was emptied or initial records were being added. * The default text encoding for newly generated database files is now UTF-8. * Fixed a nasty bug which