Message179058
Considering that sqlite's 'replace' is a synonym for 'insert or replace', I think the logic error is actually in the detect_statement_type function. Since actions are conditionally taken on the REPLACE statement type in the code, including at least one that adjusts the lastrowid, I don't think the fix for lastrowid is as simple as just always setting it. But I'm not that familiar with sqlite internals, so perhaps someone with more knowledge will weigh in. |
|
Date |
User |
Action |
Args |
2013-01-04 17:55:48 | r.david.murray | set | recipients:
+ r.david.murray, jim_minter |
2013-01-04 17:55:48 | r.david.murray | set | messageid: <1357322148.2.0.722759508132.issue16864@psf.upfronthosting.co.za> |
2013-01-04 17:55:48 | r.david.murray | link | issue16864 messages |
2013-01-04 17:55:47 | r.david.murray | create | |
|