Re: [sqlite] Checking for read-only

2004-03-09 Thread Steve Palmer
Hmm... I don't get an error when I execute that statement (substituting appropriate table name and also field name) against a r/o database. Specifically: SQLite version 2.8.13 Enter ".help" for instructions sqlite> update info set version=1; SQL error: attempt to write a readonly database

Re: [sqlite] Checking for read-only

2004-03-09 Thread D. Richard Hipp
Steve Palmer wrote: > I was going by the comment at http://www.sqlite.org/c_interface.html which > says: > > "If the file is read-only (due to permission bits or because it is located on > read-only media like a CD-ROM) then SQLite opens the database for reading > only." > > I don't know how true

Re: [sqlite] Checking for read-only

2004-03-09 Thread Steve Palmer
I was going by the comment at http://www.sqlite.org/c_interface.html which says: "If the file is read-only (due to permission bits or because it is located on read-only media like a CD-ROM) then SQLite opens the database for reading only." I don't know how true this is but I assume that since

Re: [sqlite] Checking for read-only

2004-03-09 Thread Peter
Steve Palmer wrote: Is there an easy way I can open a database via sqlite_open and then find out if sqlite has opened it in read-only mode without first needing to do any sort of modification and get an error code? I want to adjust the UI in my application to disable certain functionality if the

[sqlite] Checking for read-only

2004-03-09 Thread Steve Palmer
Is there an easy way I can open a database via sqlite_open and then find out if sqlite has opened it in read-only mode without first needing to do any sort of modification and get an error code? I want to adjust the UI in my application to disable certain functionality if the database is

Re: [sqlite] Inner join problem

2004-03-09 Thread Simon Berthiaume
I once posted about that on this mailing list and one of the solution Mr DRH suggested was to auto-expand the table name ( would become SELECT * FROM ) internaly in the SQLite API, but I have no idea if any efforts were put in that direction since it could probably break the old syntax. Ce fut un

Re: [sqlite] Inner join problem

2004-03-09 Thread Guillermo Fernandez Castellanos
Sweet... works right perfect. Can it be considered as a bug? Merci beaucoup! Guille Simon Berthiaume wrote: I think I know what the problem is. SQLite doesn't like having a table name following an openint parenthesis "(" in the FROM clause. Try the following statements instead: SELECT main.id,

Re: [sqlite] Inner join problem

2004-03-09 Thread Simon Berthiaume
I think I know what the problem is. SQLite doesn't like having a table name following an openint parenthesis "(" in the FROM clause. Try the following statements instead: SELECT main.id, prim.primname, sec.secname FROM main INNER JOIN sec ON

[sqlite] Inner join problem

2004-03-09 Thread Guillermo Fernandez Castellanos
Hi, I've had problems with inner join transactions. Here is what I do: I create the tables: sqlite> create table main ( ...> id integer primary key, ...> primid int(10), ...> secid int(10) ...> ); sqlite> sqlite> create table prim ( ...> primid integer primary key, ...>

AW: [sqlite] SQLite 2.8.13. Issues found with SQLite.exe

2004-03-09 Thread michael.hanssen
Hi all, my tests found: Using a file test.sql and decommenting the .commands as required -- + .databases -- + .dump -- + .echo ON -- + .exit -- + .explain -- + .header ON -- + .help -- + .indices table -- + .mode list -- +

[sqlite] Finding the Bug fixes in a new version

2004-03-09 Thread Avner Levy
Every time a new version of sqlite is released I need to go over all the bugs that were fixed to that release and decide if there is a good reason to move up to the new version. Is there a easy way for getting the list of all bugs fixed to 2.8.13 (for example) ? I've looked in the report