Hmmm I'm afraid we have combined the Mysl dataconnector with Corelabs and somwhere mysql interprets the ^@ literally...Not always.
We are performing test , but in a simple form with one dataset and Mysqldataadapter I cannot get it to go wrong
Thanks anyway for looking at the problem and it may be an issue
Hi,
I have noticed that when I look in the mysql-slowquery.log that all Queries passed to the server by the Corelab MysqlDirect.NET library have ^@ at the end.
(This does not happen by the way with the Corelab MyDac for borland C++ builder)
Untill today it has not caused any problems however now I a query
That looks like select BildNr from v_Anzeigenbilder where SUBSTRING(BildNr,3,4) = "2656"^@;
Where the end is a string in the mysql client this returns an empty set.
While without the ^@ it returns one record (which is correct).
Easy to generate make a table with at least one char field
CREATE TABLE `testaa` (
`id` int(11) NOT NULL,
`name` char(64) default NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
INSERT INTO testaa VALUES(1,"Alligator Descartes");
INSERT INTO testaa VALUES(2,"Tim Bunce");
select name from testaa where SUBSTRING(name,1,2) = 'Al'^@;
gives me an empty set
select name from testaa where SUBSTRING(name,1,2) = 'Al';
gives me the correct set
Mysql 5.0.21