Re: MySQL Workbench ALTER VIEW bug? when using hexadecimal values
Anyway, thanks for your response Jerry.
Indeed - though the definition of "multiple values" here is probably open to interpretation. Is a datetime field non-normalised because it contains a day and a month and a year and an hour and a minute and a second?
In my case, the 96-bit field is a code, as read (from an RFID tag as it happens). So I store the code, *as read*, in a single field in a table, and then do the decoding via a view on that table. This enables me to manipulate the various encoded values in different ways. If I change the way in which I manipulate the value, or add extra conditions, I can (rather, should) just be able to change the view code without changing the underlying table or its data.
In a more generalised sense, I suspect hex codes in a view may always get truncated, though I need to demonstrate that. If so, I'm a little surprised if no-one's found it yet! Then I'll see about reporting it.
Received on Mon Apr 25 2016 - 09:59:54 CEST
Original text of this message