ODBC 3.51 Windows + Delphi - metadata problems

description of the bug

When using the ODBC 3.51 Windows version with Delphi the ODBC driver seems=
to randomly return incorrect metadata. For instance, a MySQL field VARC=
HAR 12 is reported to Delphi as a type MEMO, or LONGTEXT - which I use fo=
r MEMO - may be reported as a varchar (or string) type, rather than memo=
or blob.

This causes major problems with 3rd party controls like Report Builder (whi=
ch applies "Autostretch" to memo fields but not string fields, so my memo=
fields aren't printing properly as Delphi thinks they are strings - but =
only in some instances!!). These products work OK with Delphi ADO and Ac=
cess or MS SQL server, so I can only assume the MySQL ODBC is causing the=
problem.


instructions

Install ODBC 3.51 on Windows, with Delphi 5 Enterprise. Set up an ADO conn=
ection of type ODBC to the MySQL ODBC. Add a Delphi ADO query component.=
Add all the fields, and look at the data type.=20

howto repeat the behaviour

Follow the above instructions.

THanks for your help

Barry
Dr Barry Clark
Senior Lecturer, Medical Education Unit
11 Southpark Avenue
University of Glasgow
Glasgow G12 8LG

------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12132@lists.mysql.com
To unsubscribe, e-mail

RE: ODBC 3.51 Windows + Delphi - metadata problems

Hi,

>
> description of the bug
>
> When using the ODBC 3.51 Windows version with Delphi the
> ODBC driver seems to randomly return incorrect metadata. For
> instance, a MySQL field VARCHAR 12 is reported to Delphi as a
> type MEMO, or LONGTEXT - which I use for MEMO - may be
> reported as a varchar (or string) type, rather than memo or blob.

This is never be the case of returning LONGTEXT or MEMO for
VARCHAR type, because driver returns SQL_VARCHAR for this.

By the way, previous versions(2.50 and 3.51) of MyODBC use
to return some misc results in SQLGetTypeInfo to bypass
ACCESS to work fine, which used to return multi-results.
But I fixed them in 3.51.03. Can you please cross check
with that version.

Also, lot of users are using Delphi, but I never saw a case
of this error. So, it will be good if you can also send me
the ODBC (DM) Trace for the Delphi when you get the above
error.

Thanks.

Regards, Venu
--
For technical support contracts, go to https://order.mysql.com
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Venu
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Developer
/_/ /_/\_, /___/\___\_\___/ California, USA
<___/ www.mysql.com


>
> This causes major problems with 3rd party controls like
> Report Builder (which applies "Autostretch" to memo fields
> but not string fields, so my memo fields aren't printing
> properly as Delphi thinks they are strings - but only in some
> instances!!). These products work OK with Delphi ADO and
> Access or MS SQL server, so I can only assume the MySQL ODBC
> is causing the problem.
>
>
> instructions
>
> Install ODBC 3.51 on Windows, with Delphi 5 Enterprise. Set
> up an ADO connection of type ODBC to the MySQL ODBC. Add a
> Delphi ADO query component. Add all the fields, and look at
> the data type.
>
> howto repeat the behaviour
>
> Follow the above instructions.
>
> THanks for your help
>
> Barry
> Dr Barry Clark
> Senior Lecturer, Medical Education Unit
> 11 Southpark Avenue
> University of Glasgow
> Glasgow G12 8LG
>
> ------------------------------------------------------------ ---------
> Before posting, please check:
> http://www.mysql.com/manual.php (the manual)
> http://lists.mysql.com/ (the list archive)
>
> To request this thread, e-mail bugs-thread12132@lists.mysql.com
> To unsubscribe, e-mail
>



------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)

To request this thread, e-mail bugs-thread12134@lists.mysql.com
To unsubscribe, e-mail