[sqlite] Re: Probably, bug in SQLite (Or, what is wrong with this query?)

> Does these queries work on other databases? I can test only MS SQL Server today, and the original query generates error. IMHO, the bug is in both SQLite and MS SQL Server :) > Are they valid correlated subqueries? I think, yes.

Re: [sqlite] Probably, bug in SQLite (Or, what is wrong with this query?)

Cory Nelson wrote: > > Can anybody tell me, what is wrong with this simple query: > > > >select a, (select c > > from (select b + 1 as c) as Table2) as d > >from (select 1 as a, 2 as b) as Table1 > > I don't claim to be a master of SQL, but isn't "select b + 1 as c" its >

[sqlite] Probably, bug in SQLite (Or, what is wrong with this query?)

Hello! Can anybody tell me, what is wrong with this simple query: select a, (select c from (select b + 1 as c) as Table2) as d from (select 1 as a, 2 as b) as Table1 The error arise at line 2 ("no such column: b"). AFAIK, the syntax is perfectly correct. This error arise

Re: [sqlite] proposal for improving concurrency in SQLite

Hello! I think, there is another way for high-concurrency SQLite-based systems. **It is not entirely universal**, but I hope it may be used for high-traffic web sites and similar kind of systems, where each individual transaction (such as a page retrieval or a form submission) is very short and

Re: [sqlite] Error: database or disk is full

Anton Kuznetsov wrote: > I use SQLite 3.2.8. > > When comitting a transaction I get an error "database or disk is full". But > there is 6 Gb of free space on my hard drive. Database is about 4 Gb. > There is no error when doing the same inserts but without transaction. > > Why does it happen?

[sqlite] Can I have access to in-memory DB from different threads?

Hi, all! Can I have access to in-memory DB from two different threads? Best regards, Alexander mailto:[EMAIL PROTECTED]

Re: [sqlite] Usability problem with quoted names

D. Richard Hipp wrote: > The rule in SQLite is > that a column name (or table name) can be any sequence of > characters that does not include US-ASCII punctuation or > control characters and does not begin with a digit. It is cool! I have not seen this in SQLite documentation > Note also that

Re: [sqlite] Usability problem with quoted names

Teg wrote: > Why not use "?" then fill it in the the actual value later? Quoting > and having to actually look at values to make sure they were legal > gave me no end of problems now I: > ... > I never pass any kind of quoted values any more. I'm sorry, my previous post is quite obscure. This

[sqlite] Usability problem with quoted names

Hi! If I use "some double-quoted stuff" in my query, this one can have two absolutely different meanings. Usually it is column name, but if I wrote this string with error, it silently converts into string literal. I think, this silent behaviour is not very good. If it happens inside deeply

Re: [sqlite] qmark style updates

The second parameter of cursor.execute() accept **sequence** of bindings. Try this: c.execute(toDo, [s1]) > from pysqlite2 import dbapi2 as sqlite > > con = sqlite.connect("mydb.db") > c = con.cursor() > > s1 =3 > toDo ="Update ex set amount = ? where ex_id = 1" >

Re[2]: [sqlite] Unsupported SQL feature

> > select * from t1 where a >= ALL (select b from t2) > > What are these constructs suppose to do? """ QUANTIFIED SUBQUERIES A quantified subquery allows several types of tests and can use the full set of comparison operators. It has the following general format: value-1