Closed E-gy closed 1 year ago
Could you share the DDL of the table ? was there any TIME column in there ?
After checking code, this might be https://jira.mariadb.org/browse/CONJS-236
it will be corrected with 3.1.0 release (commit https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/be84cc4403f95cbcb80380d94866399e94f21c3f )
Error occurs when trying to
execute
a particularSELECT
query.Stack trace:
Tested on MariaDB version 3.0.0-3.0.2, Node 16, on both Windows and Linux (the above trace is from Win).
I haven't yet been able to discern the exact specificity of the query that causes the crash - it seems to be both related to the table and the data stored - as it crashes on particular column of particular row in particular table. As simple as it is the query in question returns a complete result set of a single item - it looks like this:
Running with
query
instead ofexecute
simply returnsundefined
, with no errors whatsoever reported anywhere.Finally and obviously, running the query in MySQL works as expected and returns the singled intended item correctly.
As a temporary fix, i'm returning the minimum columns required, which happen not to cause the crash, altho permanently it won't be possible to keep this behaviour due to service requirements.