FengTao DING <hwk...@motorola.com> wrote: > I prefer to one connection rather than WAL if it can accomplish the job. > > But I found that, INSERT can be done in one connection, but UPDATE can not. > > Because in my UPDATE case, the new values that will be updated come from > another different table, and the UPDATE's WHERE condition also involves > columns from more than one tables(actually 3),
How does this prevent you from running an UPDATE statement on the first connection, while still enabling you to do this on the second? I don't understand the nature of the problem. > UPDATE statement doesn't support JOIN, so I didn't find a way to do this in > one connection(one query). Where there's a will, there's a way. Show your database schema, describe exactly what kind of change you want to make. > Currently, the only way I can work out is that, > save all SELECT result in a heavy c++ array ( include values that WHERE > needs ), then use the same connection to do the UPDATE, but this should not > be a smart way. Could anyone point out me another method? Not without some more details. -- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
