Alboni Messages: 216 Registered: January 2012 Location: Kajaani, Finland
Experienced Member
Hello, I see some issue with SqLite3 lately that didn't exist before.
They have to do with the datatype of the results of a query.
issue 1 : SqlMax(some time column) returns WSTRING_V result instead of TIME_V
issue 2 : Selecting a BOOL column also returns WSTRING_V result instead of BOOL_V
again, it only applies to SqLite, on MySql it works correctly
Hello, I see some issue with SqLite3 lately that didn't exist before.
They have to do with the datatype of the results of a query.
issue 1 : SqlMax(some time column) returns WSTRING_V result instead of TIME_V
issue 2 : Selecting a BOOL column also returns WSTRING_V result instead of BOOL_V
again, it only applies to SqLite, on MySql it works correctly
I enclosed an example
BOOL behaviour is as expected (BOOL in .sch is always emulated by text column to be consistent across all DBs).
Well, that is rather nasty inconsistence with MySql.... Sorry, long time ago MySql was contributed package and I missed this one. Cannot fix that now without breaking existing code
That said, maybe we could introduce a new schema type, e.g. "LOGICAL" that maps to bool and uses database 'bool' where possible and smallest number where not possible?