Gary, I'm really new to ruby and DM so this might be wrong, but it worked for me.
I ran into a similar problem with sqlite3 moving from some test code to 1.0.0 and found the solution in the DM 1.0.0 release notes, with the changes to the data objects and adapters, and the need to 'gem install' them separately. Specifically: ==== For example if you want to use sqlite, do: $ gem install dm-sqlite-adapter This should pull in data_objects and do_sqlite3 automatically, so no need to specify either of those explicitly anymore. " ==== Good catch on the LIMIT vs count(*) BTW. Cheers Eric On Jun 23, 6:23 am, Gary Yngve <[email protected]> wrote: <snip> > (Also, I'd post this in lighthouse if I could figure out how to get > sqlite3 adapter to work w/ 1.0... > I tried DataMapper.setup(:default, 'sqlite3::memory:' > but that complained that it couldn't find the adapter.. am i missing a > require? <snip> -- 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.
