Re: DBD::mysql retrieving column collation
Patrick Galbraith <[email protected]> Fri, 06 Jul 2007 17:17:27 +0300
| Newsgroups | gmane.comp.db.mysql.perl |
|---|---|
| Message-ID | <[email protected]> |
I don't know offhand if with DBI, you should be able to get this info. It seems pretty easy to add. regards, Patrick Paul DuBois wrote: > At 6:59 AM +0100 7/6/07, John ORourke wrote: > >> Paul DuBois wrote: >> >>> If you resort to parsing SHOW output, you might find the output of >>> SHOW COLUMNS easier to deal with, because it's in row-and-column >>> format. SHOW FULL COLUMNS displays an additional Collation column, >> >> Thanks! I wasn't aware of SHOW FULL COLUMNS. >> >> However I'm now successfully using the new information_schema >> database like this: >> >> "select data_type,collation_name from information_schema.columns >> where table_schema=? and table_name=? and column_name=?" >> >> Then if collation_name =~/bin/ it's a binary column. > > > Yes, you can use information_schema if you can assume MySQL 5.0 > or higher. But your rule for determining binary string columns > is incorrect. > > collation_name =~/bin/ is a non-binary column with a binary *collation*. > Not the same thing as a binary string. Binary strings have > a data type of binary, varbinary, or blob, and the collation > is NULL. > -- Patrick Galbraith, Senior Programmer Grazr - Easy feed grazing and sharing http://www.grazr.com Satyam Eva Jayate - Truth Alone Triumphs Mundaka Upanishad -- MySQL Perl Mailing List For list archives: http://lists.mysql.com/perl To unsubscribe: http://lists.mysql.com/[email protected]