On Tue, 14 Feb 2017 07:57:17 -0500
Richard Hipp wrote:
> It does not ignore it, it overwrites it. The ".mode" command now
> always also sets the ".separator" (to the default separator value) for
> those modes where the separator is used. This was added to work
> around the unexpected behavior d
On Tue, 14 Feb 2017 02:16:50 -0200
Dâniel Fraga wrote:
> The solution was to provide the ".separator ," again after
> ".mode line", but it seems redundant, since I already had specified it
> in the "-init" file.
Sorry, I mean ".mode
3.17.0 release brings the following change:
In the command-line shell, enhance the ".mode" command so that it
restores the default column and row separators for modes "line",
"list", "column", and "tcl".
***
I use the sqlite command-line shell with the option -init
pointi
On Wed, 31 Dec 2014 22:18:02 -0500
Igor Tandetnik wrote:
> Well, the WHEN condition on the trigger is always false when the table
> is empty. What else did you expect?
>
> Perhaps you meant something like
>
> WHEN new.last_price NOT IN (SELECT last_price ...)
Ops, you're right ;). Sor
I found a solution to a problem I reported here:
http://stackoverflow.com/questions/27711987/sqlite-insert-only-if-price-is-different-from-last-row/
And I notice an SQLite abnormal behaviour (I'm using version
3.8.7.4). Here's how you can reproduce it:
1) create a TABLE a
5 matches
Mail list logo
