Nelson, Erik - 2 Sent: Saturday, December 16, 2017 5:27 PM
>Petern wrote on Saturday, December 16, 2017 4:53 PM
>>Re: Nelson "odd". This will make the desired (?) side effect happen:
>>.load eval.so
>>SELECT coalesce(eval('INSERT INTO table1 VALUES(a, b, c)'), 1) AS value;
>>If INSERT references columns from an outer scope then use printf() inside the
>>eval().
>>That one is eval(X,Y) where Y is optional column separator. If you need
>>the improved eval(X,Y,Z) where Z is an optional line separator, let me know
>>and I'll post that upgrade.
>That's a great suggestion... I'm not using the sqlite shell and I don't have
>control of the application but there's a reasonable chance that eval() is
>statically compiled into the app. I'll investigate that further.
I tracked this down, 'eval' isn't available. :( My only input possibility is
sql statements/pragmas... anything that will pass through a prepare()/step()
and produce at least one row of results.
Thanks for the suggestion, though... I never would have thought of trying that!
----------------------------------------------------------------------
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
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
