just to hit back on this for anyone else here..
namelessjon offered this advice:
* do the dm connection stuff in config/init.rb
Merb::BootLoader.after_app_loads do
if Merb.environment.eql? "development" then
DataMapper.setup(:default, 'mysql://myuser:myp...@myhost/myproj_dev');
DataMapper.finalize
else
DataMapper.setup(:default,
'mysql://myuser:myp...@myhost/myproj_production'); DataMapper.finalize
end
# ......
then... dupe you auto-upgrade task ...
have mine in lib/tasks/custom.rake
desc "auto-upgrade replacement"
task :auto_upgrade => :merb_env do
DataMapper.auto_upgrade!
end
-ian
On 11:42 Mon 14 Jun , ian wrote:
> curious if anyone is using merb 1.0.0 w/merb yet? seems like
> merb_datamapper is conflicting with dm-migrations.
>
> pretty sure dm-migrations does auto-upgrade rake task; sets up the db
> connection and so forth right?
>
> current merb stack is 1.1.0.pre and was upgrading from dm 0.10.2
>
> --
> You received this message because you are subscribed to the Google Groups
> "merb" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/merb?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"merb" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/merb?hl=en.
