I think this is a bug. However, looking at the code the way to achieve that is to surround the string in double quotes which will cause exactly what appears between the double-quotes to be stored. I think it is because of the way the parsing and mprintf function works ...
sqlite> .param init sqlite> .parameter set :date "'2019-11-15'" sqlite> .param list :date '2019-11-15' sqlite> select :date; 2019-11-15 sqlite> select datetime(:date); 2019-11-15 00:00:00 -- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-----Original Message----- >From: sqlite-users <sqlite-users-boun...@mailinglists.sqlite.org> On >Behalf Of Shawn Wagner >Sent: Friday, 15 November, 2019 10:15 >To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> >Subject: [sqlite] sqlite3 shell .parameter command evaluating arguments >when it shouldn't. > >Consider: > >sqlite> .parameter init >sqlite> .parameter set :date '2019-11-15' >sqlite> .parameter list >:date 1993 > >How do I make it treat the value argument as a string and not as a >numeric >expression that gets evaluated? >_______________________________________________ >sqlite-users mailing list >sqlite-users@mailinglists.sqlite.org >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
