Devart Forums

Hi,

On MySQL 5.0.51a (community edition) and MyDAC 5.20.0.12 the command SHOW ENGINES fails fetching the data correctly, this is the output:

# | Engine| Support| Comment
--+-------+--------+---------------------------
1| MyI | YES | Default engine as of MySQL
2| MEM | YES | Hash based, stored in memo
3| Inn | DEF | Supports transactions, row
--+-------+--------+---------------------------
4| Ber | NO | Supports transactions and
5| BLA | YES | /dev/null storage engine (
6| EXA | YES | Example storage engine
--+-------+--------+---------------------------
7| ARC | YES | Archive storage engine
8| CSV | NO | CSV storage engine
9| ndb | NO | Clustered, fault-tolerant,
--+-------+--------+---------------------------
10| FED | YES | Federated MySQL storage en
11| MRG | YES | Collection of identical My
12| ISA | NO | Obsolete storage engine


As you can see, the data is being cut off!

A simple sample application with a TMyConnection, TMyQuery, TDataSource and TDBGrid can show this behaviour. I'm using the "direct" connection.

My database developer application fails because of this.

Please send me a hotfix!

With regards,

Martijn Tonies
Upscene Productions

We could not reproduce the problem. Please, try to download the last MyDAC build and check if this problem exists there, too.

The about box says 5.20.1.15 now (Delphi 7), but I still got the same problem.

Are you using the Direct connection mode as well?

I got this from the MySQL "internals" list:

sounds like you are using the wrong value for the length of a utf8
field, where the number of characters is being divided by the max
character length. (10 / 3 = 3, 80 / 3 = 26)

or it could be the server returning the wrong length. use "mysql
--column-type-info" to see what it is returning.

Would that help any?

--
Martijn Tonies
Upscene Productions

Same problem confirmed on Mysql 5.0.51a community and 5.0.54 enterprise on windows. Will check on linux and post the result tomorrow
On Mysql 5.0.45 community working without problem.

Same problem confirmed with version 5.0.54 on linux.

Thank you for information. We have reproduced this problem and fixed it. This fix will be included in the next MyDAC build.

What was the error? Can you post the fix?

--
Martijn Tonies
Upscene Productions

The problem appears because MySQL 5.0.51a calculates fileds length incorrectly.
We have send you the fix by e-mail.

How come when sending the same request "Show Engines"to Mysql browser GUI, we get the expected result not truncated ?

Thanks for the fix.

Any idea why it worked in previous versions?

How about MySQL 5.1 or 6.0?
--
Martijn Tonies
Upscene Productions

Dimon,

Could you send me the fix too ?

The problem is connected with the some of the MySQL versions incorrect behaviour.
In MySQL 5.1 and 6.0 this problem was not discovered.