JRuby

rename column in jdbcmysql driver does not preserve default and null constraints in Rails migrations

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Incomplete
  • Affects Version/s: JRuby 1.3.1
  • Fix Version/s: None
  • Component/s: JRuby-extras
  • Labels:
    None
  • Environment:
    activerecord-jdbcmysql-adapter v 0.9.1, Rails 2.2.2
  • Number of attachments :
    0

Description

To reproduce: Make a dummy rails 2.2.2 app. Create first migration to create a table with float column having a default value and not null. Make a second migration renaming the column. The default constraints are not included on the generated ALTER TABLE rename command.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Nick Sieger added a comment -

If you could make a test case out of this, that would be great. See the file test/mysql_nonstandard_primary_key_test.rb in ar-jdbc source for some hints.

Show
Nick Sieger added a comment - If you could make a test case out of this, that would be great. See the file test/mysql_nonstandard_primary_key_test.rb in ar-jdbc source for some hints.
Hide
Permalink
Charles Oliver Nutter added a comment -

Very old, ar-jdbc has had many releases, no follow-up to request, and this should be filed with ar-jdbc anyway.

Show
Charles Oliver Nutter added a comment - Very old, ar-jdbc has had many releases, no follow-up to request, and this should be filed with ar-jdbc anyway.

People

  • Assignee:
    Charles Oliver Nutter
    Reporter:
    Chad Woolley
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: