Jdbcmysql driver not respecting column defaults from migrations

Ruby JRuby
1

Hello,

Please let me know if there’s a better list for this question.

In Rails, we are using the jdbcmysql driver from the
activerecord-jdbcmysql-adapter gem v 0.9.1. Some of our migrations
have defaults set for columns, e.g.:

t.float “columnname”, :default => 1.0

Under the ruby mysql driver this properly sets the column default in
the DB, but under the jdbcmysql driver it does not.

There are similar problems with :null => false on datetime fields.

We’ve googled briefly and checked the JRuby JIRA, but didn’t find
anything related. Any ideas? Is the JRuby JIRA the correct place to
report this bug?

Thanks,
– Chad

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
2

On Wed, Sep 30, 2009 at 12:20 PM, Chad W. [email protected]
wrote:

Under the ruby mysql driver this properly sets the column default in
the DB, but under the jdbcmysql driver it does not.

This seems to be a bug where rails migrations which rename columns do
not have defaults correctly set on the generated ALTER TABLE query.
Bug opened:

http://jira.codehaus.org/browse/JRUBY-4024

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
3

Here is another bug we found, where schema dump of multi-column
indexes containing the id column is missing the id in the dumped
create_index command:

http://jira.codehaus.org/browse/JRUBY-4025

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
4

And another related bug on schema dump of limit for longtext fields in
mysql, for all you googlers:

http://jira.codehaus.org/browse/JRUBY-4026

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email