When getting column information about a table that contains text columns the column info is returning that it's a blob. I don't know if this is an issue with the python portion, the mysql portion, or what--mysql jdbc drivers can tell the difference; why doesn't pymysqldb?
Thanks much!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-10-02
> RTFM the MySQL docs and you see that TEXT == BLOB
Yet JDBC can tell the different, so obviously there _is_ a difference. I just want to know what it is and why I can't access it.
As far as RingTFM, I have been. The mysql JDBC driver is returning a -1 for (LONGVARCHAR) for text fields and -3 (VARBINARY) for blobs. pyMysqldb is returning a 252 for both types.
As I said in my original message, JDBC knows; I want to know how. If you don't know, just say so, it's okay.
Thanks (sorta),
Dave
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When getting column information about a table that contains text columns the column info is returning that it's a blob. I don't know if this is an issue with the python portion, the mysql portion, or what--mysql jdbc drivers can tell the difference; why doesn't pymysqldb?
Thanks much!
RTFM the MySQL docs and you see that TEXT == BLOB
> RTFM the MySQL docs and you see that TEXT == BLOB
Yet JDBC can tell the different, so obviously there _is_ a difference. I just want to know what it is and why I can't access it.
As far as RingTFM, I have been. The mysql JDBC driver is returning a -1 for (LONGVARCHAR) for text fields and -3 (VARBINARY) for blobs. pyMysqldb is returning a 252 for both types.
As I said in my original message, JDBC knows; I want to know how. If you don't know, just say so, it's okay.
Thanks (sorta),
Dave
Most likely it is due to the ODBC driver. There is some MySQL connect option, iirc, that makes it more "ODBC-friendly"; check the MySQL docs.
Hmm, yeah; I don't know how to deal with that in my python module. I guess I'll just skip it for now and configure my code some other way.
Thanks,
Dave