> Unfortunately, this is not true for SQLite3. If you execute the following SQL
> commands
>
> CREATE TABLE t (a REAL, b REAL);
> INSERT INTO t VALUES (5, 2);
>
> both values are stored as INTEGER and not as REAL as one would expect
> by the column affinity. In fact, this behaviour is
Hello, SQLite developers!
Sorry for my bad English.
I use SQLite (great program!), and encounter some unicode problems.
I think, this problems not with dbms kernel, but with command-line
utilite.
So far as SQLite supports unicode, I want at least enter russian
strings into table rows and
> I want to avoid doing a two step process outside the db... I want to
> insert a row only if it doesn't exist already.
IMHO, if you table T1 have a unique key, you may do this
INSERT OR IGNORE T1 VALUES(1, 2, 3);
Best regards,
Alexandermailto:[EMAIL PROTECTED]
Yes, I understand now.
Thanks for explanation!
Best regards,
Alexander mailto:[EMAIL PROTECTED]
> SQLite transactions are always serializable.
Serializable mode requires two-phase locking protocol. In practice
it means all locks (for read and for write) hold until transaction
end.
Deferred transaction drop SHARED lock in middle of transaction
and replace it with
5 matches
Mail list logo