Keith Medcalf Sent: Sunday, December 17, 2017 4:30 PM
>How do you know the insert is not working? Have you verified that the data is
>not being inserted or are you simply relying on a popup provided by the
>application? If the later, you should be aware that the application can
>pop-up whatever it wants at any time.
The insert() does work when step() is called.
>For example, it could claim the statement failed because the moon is not made
>of blue stilton. While the moon is indeed not made of blue stilton, that is
>not (and cannot possibly be) the reason that the statement failed. It does
>not mean that the statement in fact failed at all, only that the application
>popped up a pop saying it failed bue to the moon not being made of blue
>stilton.
Also correct- the application effectively does "if (sqlite3_column_count() ==
0) throw("the moon is made of blue stilton")
>By the time the "application" knows that no results were returned it is
>already too late, the statement has already been run to completion. The
>application is likely just "spitting out a message" based on their being no
>results.
Exactly. The statement is run, and it runs correctly. Just the application
halts the run because sqlite3_column_count() is zero.
>Unless of course the application has been deliberately designed to preclude
>insert/update statements by wrapping each statement execution in a
>transaction, which it then does a rollback on.
That's not the case, it's just a poor assumption on the part of the application
designers that sqlite3_column_count() > 0
>Or perhaps by making sure the first token of the statement is the word
>"SELECT" ... If this is the case then perhaps you can get a version of the
>application that does not have these, rather intentionally created,
>restrictions.
Right- hence the 'For unfortunate reasons' clause. It's not possible to change
the application at this time, so I was hoping for some workaround using the
things I can control (the sql statements being fed to the application)
----------------------------------------------------------------------
This message, and any attachments, is for the intended recipient(s) only, may
contain information that is privileged, confidential and/or proprietary and
subject to important terms and conditions available at
http://www.bankofamerica.com/emaildisclaimer. If you are not the intended
recipient, please delete this message.
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
