Quantcast
Channel: Toad for MySQL
Viewing all articles
Browse latest Browse all 1315

Forum Post: Hexadecimal Literals

$
0
0
I'm having a persistent problem where whenever running any automated script building within Toad for MySQL, it is choosing to export binary data as a hexadecimal literal, which would be fine, but these appear to not be formatted correctly (data comparison for example). As per http://dev.mysql.com/doc/refman/5.6/en/hexadecimal-literals.html literals must start with "0x", or "X'", neither of which is true. Upon running the scripts, they will error out on the page with the following error code: http://dev.mysql.com/doc/refman/5.6/en/error-messages-server.html#error_er_bad_field_error Example: UPDATE `table1` SET `column1` = 3C703E3C7374726F6E673E43... Expected: UPDATE `table1` SET `column1` = 0x 3C703E3C7374726F6E673E43... Disabling Hex literal usage in toad would fix it, or perhaps there is some setup/config that is incorrect? Any help would be appreciated. TIA.

Viewing all articles
Browse latest Browse all 1315

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>