Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.

Export with JSON field seems to be buggy

kisb's profile image kisb posted 4 years ago in Import/Export Permalink

dear all,

Im exporting my database with JSON field, the result:

INSERT INTO * VALUES (**, 1, [138, 100, 800, 419]));

but shouldn't it be look alike:

INSERT INTO * VALUES (**, 1, '[138, 100, 800, 419]'));

? At least, importing the first one causes syntax error

enduro44's profile image enduro44 posted 3 years ago Permalink

We are useing Export feature a lot in our projects. And I can confirm, that exporting tables with json field results in INSERT INTO * VALUES (**, 1, [138, 100, 800, 419])); Which results in syntax error. With this bug export feature is useless.

enduro44's profile image enduro44 posted 3 years ago Permalink

I'm using HeigiSQL 9.3.0.5104

Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.
ansgar's profile image ansgar posted 3 years ago Permalink

Yes, confirmed.

Code modification/commit c230156 from ansgarbecker, 3 years ago, revision 5106
Use exact text data types instead of their whole category for detecting special binary columns. Fixes unquoted JSON content in SQL exports. See http://www.heidisql.com/forum.php?t=20655
ansgar's profile image ansgar posted 3 years ago Permalink

Should be fixed in r5106

enduro44's profile image enduro44 posted 3 years ago Permalink

Thank you. I can confirm that problem is fixed in r5106.

globalassignmenthelp's profile image globalassignmenthelp posted 3 years ago Permalink

aaa

Please login to leave a reply, or register at first.