>> In my code I want to read from one table and write the results to >> another table. But if I don't fetch all the results and close the >> reading connection, I cannot write to another table in the same >> database. > > Do it all from the same connection. The locks are "owned" by a > database connection, so opening a second connection won't work, even > if they're within the same process. > > You should, however, be able to run both the query and the inserts > from the same connection without issues, even if they're intermixed.
Thanks for all the answers! I know how to solve this problem now. But there is one thing that is still unclear to me: why did this work in SQlite2? Was Version 2 unsafe when executing such a pattern? Andreas _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
