You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
my table has a poi_info column,that type is varchar ,i save a json string into this column
this is the string: { "locationCode": "A4-201\\202\\206"}
when i use ToSQL func, it give me SQL like this:
INSERT INTOelement (location_code) VALUES ( '{"locationCode":"A4-201\\202\\206"}' );
it seems evrything was ok,
when i execute this SQL
the database data become:
{ "locationCode": "A4-201\202\206"}
the \ beacome \ by database (MySQL 5.7)
so that will get an error when use json.Unmarshal() unmashal error invalid character '2' in string escape code
instead , ToSQL should give me a SQL like this:
The issue has been automatically marked as stale as it missing playground pull request link, which is important to help others understand your issue effectively and make sure the issue hasn't been fixed on latest master, checkout https://github.com/go-gorm/playground for details. it will be closed in 30 days if no further activity occurs. if you are asking question, please use the Question template, most likely your question already answered https://github.com/go-gorm/gorm/issues or described in the document https://gorm.io ✨ Search Before Asking ✨
my table has a poi_info column,that type is varchar ,i save a json string into this column
this is the string:
{ "locationCode": "A4-201\\202\\206"}
when i use ToSQL func, it give me SQL like this:
INSERT INTO
element(
location_code) VALUES ( '{"locationCode":"A4-201\\202\\206"}' );
it seems evrything was ok,
when i execute this SQL
the database data become:
{ "locationCode": "A4-201\202\206"}
the \ beacome \ by database (MySQL 5.7)
so that will get an error when use json.Unmarshal()
unmashal error invalid character '2' in string escape code
instead , ToSQL should give me a SQL like this:
INSERT INTO
element(
location_code) VALUES ( '{"locationCode":"A4-201\\\\202\\\\206"}' );
The text was updated successfully, but these errors were encountered: