On Dec 9, 2008, at 2:27 PM, Daevid Vincent wrote:
Also, I realize you're trying to 'encode' some sort of X\Y\Z
coordinates
in that column, so perhaps a different delimiter such as the pipe "|"
character or "," would be more appropriate than a \ which has special
meanings?
That's actually how the values are in original. At this stage, I don't
want to mess around with it further. But exporting it later to another
coordinate-table, if that'll be required, is being thought of. Perhaps
the field might also get dropped. (Ups, now the wholly god of db
schema design will put rage upon me for bad designing in the first
place ... not to mention the NU** values ... :-$)
Thx for the hint! :)
Cheers,
Michael
Or possibly just split them out into separate X, Y, Z columns rather
than cramming them together like that. This would allow you to do
various trig and math functions on them easier (assuming you are
storing
coordinates for a reason).
There are basic SQL 'update' statements you could write to fix your
existing data and/or convert it to the new delimiter. This may save
you
headaches going forward.
d.
On Tue, 2008-12-09 at 12:42 +1300, SolidEther wrote:
Hi,
I'm trying to compare strings on a varchar field.
The code: 'select * from Image where `0020,0032`="-131.178600\
\107.113725\\200.064000";' returns the correct result set.
However, the code: 'select * from Image where `0020,0032` LIKE
"%-131.178600\\107.113725\\200.064%";' returns an empty set, and so
does 'select * from Image where `0020,0032` LIKE "-131\.178600\\107\.
113725\\200\.064000";'
I can't really figure out why, can anyone explain?
Thx,
Michael
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
