Is it really correct that in order to perform an INSERT, Sqlite demands that no other connections be active?
I have an application that loops through a results set and performs INSERTS. It uses the same database instance but (obviously) separate statements for each operation When the insert is attempted, SQLITE_BUSY is returned Waiting is obviously no use because the conflicting operation is in the outer loop Is this expected or am I doing something silly? Thanks Paul Clarke ********************************************************************* Notice: This email is confidential and may contain copyright material of Ocado Limited (the "Company"). Opinions and views expressed in this message may not necessarily reflect the opinions and views of the Company. If you are not the intended recipient, please notify us immediately and delete all copies of this message. Please note that it is your responsibility to scan this message for viruses. Please do not print this email unless necessary. ********************************************************************* Ocado Limited Titan Court 3 Bishops Square Hatfield Business Park Hatfield Herts AL10 9NE Tel: +44 (0) 1707 228000 Fax: +44 (0) 1707 227999 www.ocado.com _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
