Well, as i said - i still use older version of DM for my app (which is daemon, not web application). And i dont need any additional gems since they are not required for 0.10.2 version. Also, dont need migrations (db already in place)
The point is - im trying to use just previous DM stack while keeping 1.0 for tests and overview. So, i dont really have anything additional - it is almost plain ruby application. Datamapper loads first in line. Here is dump of $LOAD_PATH /usr/lib/ruby/site_ruby/1.8 /usr/lib/ruby/site_ruby/1.8/x86_64-linux /usr/lib/ruby/site_ruby /usr/lib/ruby/vendor_ruby/1.8 /usr/lib/ruby/vendor_ruby/1.8/x86_64-linux /usr/lib/ruby/vendor_ruby /usr/lib/ruby/1.8 /usr/lib/ruby/1.8/x86_64-linux . Everything in place. Not sure why it happened. On Jun 10, 4:40 pm, "Dan Kubb (dkubb)" <[email protected]> wrote: > Dan, > > > After upgrade to 1.0 my old stable application cannot recognize > > DataMapper module: > > ... > > > But still no results. The same issue. > > > Any ideas why? > > I'm not entirely sure why, but I did notice one problem. There's no dm- > mysql-adapter in your dependency list. You probably also want dm- > migrations if you're using DataMapper.auto_migrate! or > DataMapper.auto_upgrade! too. > > I assume this is a Gemfile you're using with bundler, but it could > also you specifying the gem paths using Kernel::gem provided by > rubygems. If it's the latter you probably want to require the gems > too, since the Kernel::gem command only really modifies the > $LOAD_PATH. > > -- > > Dan -- You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en.
