That's what I told the guy having the original issue to do, yes. That's not important.
My concern is why a conversion that's only supposed to happen if it's lossless is in fact happening and causing data loss. On Sun, Oct 13, 2019, 4:48 PM Igor Tandetnik <i...@tandetnik.org> wrote: > On 10/13/2019 7:25 PM, Shawn Wagner wrote: > > I wouldn't call that conversion, or any other, lossless unless it can be > > turned back into a string that's character for character identical with > the > > one that was originally inserted. > > If you want the text preserved character for character, store it in a > column with TEXT affinity. NUMERIC makes little sense for this requirement. > -- > Igor Tandetnik > > > _______________________________________________ > 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
