Re: MySQL Workbench ALTER VIEW bug? when using hexadecimal values

OK, try this:
(1) In Workbench, navigate to the schema test | Views.
(2) Right-click Views, Create Views...
(3) Edit the view so it reads:

CREATE VIEW `new_view` AS SELECT 0x1234 test1, 0x1234567890ABCDEF test2
(4) Click Apply
(5) Note that the review dialog shows the correct view:
USE `test`;
CREATE OR REPLACE VIEW `new_view` AS SELECT 0x1234 test1, 0x1234567890ABCDEF test2;
(6) Click Apply
(7) Click Finish
(8) Note that the page now shows the incorrect view:
CREATE
    ALGORITHM = UNDEFINED
    DEFINER = `root`_at_`localhost`
    SQL SECURITY DEFINER
VIEW `test`.`new_view` AS

    SELECT 0X12 AS `test1`, 0X1234567890ABCD AS `test2`

It is therefore my belief that anyone who uses hex values in a view, for whatever reason, whatever the normalisation level or otherwise of their database, will find that, if they make further edits to that view *within Workbench*, *and without correcting these mis-edits*, will find that any subsequent queries based on that view will fail. Received on Tue Apr 26 2016 - 15:19:04 CEST