I have a MySQL 5.0.21 database and some InnoDB tables that have blob
columns being used to store text. When reading these fields I get a
maximum of 19 characters returned to my application that uses MyODBC 3.51.

Is there an obvious explanation for this behavior, or is there something
within the setup of the ODBC datasource that I'm missing?

Thanks.


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

James Eaton wrote:
> I have a MySQL 5.0.21 database and some InnoDB tables that have blob
> columns being used to store text. When reading these fields I get a
> maximum of 19 characters returned to my application that uses MyODBC 3.51.
>
> Is there an obvious explanation for this behavior, or is there something
> within the setup of the ODBC datasource that I'm missing?
>
> Thanks.
>

James,

What does the DDL for the table(s) in question look like? Do you see the
same issue if you use a different storage engine? Is it possible for you
to test this issue with a different major version of MySQL like 4.1?

-Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE5ITdtvXNTca6JD8RAjhdAJ9CAWkSNN50akzdg0qMpQbbnUINPACf TQpR
kmxf7QLebX+G6b4l93YXJEs=
=3Gvf
-----END PGP SIGNATURE-----

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc [at] m.gmane.org