> Le 30 juin 2016 à 11:17, Clemens Ladisch <clem...@ladisch.de> a écrit : > > A better way is to try the UPDATE first, and if the data was not found > (number of affected rows is zero), do the INSERT. Doesn't even need > a comment.
Indeed. That is precisely what we do. And what is not so easy in complex programming where you have thousands of more important things to care for, in addition to handle such double statement where they make sense: >> Of course writing straight code in C/C++ it's rather simple to emulate >> situations where you want to update some values in an existing row, creating >> the row if needed. Though in larger programming tasks that ends up being >> rather tedious for business logic programmers. We hide this inside our C++ >> shell around SQLite C API and the solution is not bad but had some >> challenges for handling parameters to the statement(s) without risking them >> to be evaluated twice when re-using them for two distinct SQLite statements >> (while there is only one 'upsert' at the C++ logical level). Besides, if you ever have to write a scripts for the command line tool, you're stuck trying to emulate that semantic. Or can we check by script the outcome of the UPDATE? -- Meilleures salutations, Met vriendelijke groeten, Best Regards, Olivier Mascia, integral.be/om _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
