On Mar 14, 2015, at 6:45 PM, Richard Hipp <drh at sqlite.org> wrote:
> On 3/14/15, Skip Montanaro <skip at pobox.com> wrote: >>> >> Then I retrieved that statement with Ctl-P, then clear the id with Ctl-B >> ESC-Del. I then entered the id of the next record to correct, backed up and >> adjusted the date, and hit enter. >> >> Imagine my surprise when what I actually typed (without checking, >> obviously!) was something like this: >> >> update swimmeet set end="1991-04-21" where 4193; >> > > The sqlite3 command-line shell program will link against a variety of > (third-party) command-line editing libraries: > > (1) GNU readline > (2) Editline > (3) Linenoise (https://github.com/antirez/linenoise) > > Do you know which one your particular build of sqlite3 is using? > > Furthermore, it seems to me that the problem you describe has much > more to do with the command-line editing library than it does with > SQLite, does it not? Assuming there is a bug in the third-pary > command-line editing library, what could SQLite do about it? > Also, don?t use double quotes for strings. SQL specifies single quotes for strings, double quotes for identifiers (table names, column names, etc.) -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson
