On Sat, Apr 2, 2016 at 9:40 PM, Niko Tyni <nt...@debian.org> wrote: > On Sat, Apr 02, 2016 at 12:10:31PM +0200, László Böszörményi wrote: >> Its first parameter is the function the call and the second is the >> expected result[1]. If I use sqlite3 3.11.1, then the function returns >> an array, but not [666]. With sqlite3 3.12.0 it returns the expected >> [666]. > > The root cause is that sqlite3_column_decltype() quotes its output in > 3.12.0, where previously it didn't. [...] > So is this an intentional change or a regression? I'm not its maintainer, but will ask upstream. The only change I've found states[1]: "The sqlite3_column_decltype() routine should return NULL, not an empty string, if the column has no declared type."
Thanks for the test cases, Laszlo/GCS [1] http://www.sqlite.org/src/info/605eba4a756e7185
