Hi,
I have the similar problem, but simple rebuild does not fix it.
After some investigations I get the following results:
Mysql 5.x returns some fields as TYPE_NEWDECIMAL, but
libmysql-ruby1.8-2.7.1-1
does not defines MyslField::TYPE_NEWDECIMAL Ruby constant
(it is added in version 2.7.2 only):
rb_define_const(cMysqlField, "TYPE_NEWDECIMAL",
INT2NUM(FIELD_TYPE_NEWDECIMAL));
As a result, when Mysql DBD module collects names of available data
field types (Mysql.rc:272):
TYPE_MAP = {}
MysqlField.constants.grep(/^TYPE_/).each .... end
it does not include this type into the TYPE_MAP hash.
After that the module get data from the server with NEWDECIMAL field,
tries to find
corresponding data type (Mysql.rb:649), gets nil instead of Array, and
fails to get its [0] element.
And finally we get the error message, that has been reported in this bug.
Regards,
Boris Misenov
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
