Issues with dm-migrations (and dm-rails) about dm-migrations HOT 6 OPEN

I was talking to Davide on IRC

He confirmed that doing DataMapper::Property::Text instead of just Text solves the uninitialized constant Text error.

I (and I know some others who) couldn’t reproduce the issue with create/drop complaining about the backticks. I’m not sure, but aren’t they explicitly added for portability? Also, Davide couldn’t reproduce the issue anymore when trying today afternoon.

I’m not entirely sure about the last problem concerning .sub(///,’’) but I’ve tried all the db related tasks on mysql and didn’t notice any problems neither on ruby-1.8.7 nor ruby-1.9.2-preview3.

I’m not sure what new state is best for this ticket, Davide was saying that it’d be ok for him to close it. I’m assigning it to me and marking it "Hold" for now. Feel free to change.

by Martin Gamsjaeger (snusnu)

from dm-migrations.

This also effects Property classes that are shadowed by Ruby constants, such as DataMapper::Property::URI. I tried using a const_missing hook to access constants from DataMapper::Property but URI is global.

by Postmodern

from dm-migrations.

Injecting "URI = DataMapper::Property::URI" into DataMapper::Migration seems to do the trick. Of course this is in combination with a const_missing hook.

by Postmodern

from dm-migrations.

I have confirmed that the http://github.com/postmodern/dm-migrations branch has fixed this issue for Text, Boolean, and other types in dm-core. When using URI from dm-types specifying it explicitly as DataMapper::Property::URI ie column :source, DataMapper::Property::URI is a work around for the URI issue.

by Dennison Williams

from dm-migrations.

My const_missing hook has re-appeared in my fork of dm-core:

http://github.com/postmodern/dm-core/commits/postmodern

by Postmodern

from dm-migrations.

Is there a further action on this?

from dm-migrations.