Re: [sqlite] threads and last_insert_rowid()

> Understand this:  Any programming language that is built around threads is > inherently broken and should be avoided.  (I will not name names - you know > the languages I'm talking about.)  And any operating system that depends > upon threads for performance is equality busted and should also be

Re: [sqlite] threads and last_insert_rowid()

thanks everybody, especially Pavel Ivanov who did not give himself a trouble to look at the source though i did. but as far as i understand this is only applicable to current version of sqlite and future releases may change things. Jay A. Kreibich wrote: > If each thread is using its own,

Re: [sqlite] threads and last_insert_rowid()

i got following contradictory replies to my question > if i execute query like " insert into tbl( filed ) VALUES ( 1 ); Select > last_insert_rowid() as li;" would be it atomic? or it anyway would suffer > from threads? from borgan: > Hi, i think this will probably be "atomic". > What i mean

[sqlite] threads and last_insert_rowid()

hi. i need to get last insert id in multithreaded app. I use C API, actually some C++ wrap over it. if i execute query like " insert into tbl( filed ) VALUES ( 1 ); Select last_insert_rowid() as li;" would be it atomic? or it anyway would suffer from threads? -- Ruslan Mu