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
sqlite
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
sqlite
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 t
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 on
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 da
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 read-on
Hi!
I would like to know if there is a way to detect which constraint has failed
in the event of a "Constraint failed" error.
Thanks,
Roger.
- Original Message -
From: "D. Richard Hipp" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, March 09, 2004 10:40 AM
Subject: Re: AW
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
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,
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
main.se
[EMAIL PROTECTED] wrote:
select 'Hello, this is SQLite!', 123;
with the command line
"sqlite.exe" "test.db" ".read "test.sql""
under WinNT shows, that the commands
.nullvalue, .prompt and .separator
are not working a expected but providing an output like
unknown comman
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,
...> primnam
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
-- + .m
Avner Levy wrote:
> 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 looke
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 section
15 matches
Mail list logo