Richard, > Just to be clear, I got my Sinatra app, which used sqlite & DataMapper > running transparently on MRI & JRuby. So if anyone else is having this > problem - it > can be done, and quite easily too. Its just a documentation issue. The issues > arise due to the complexity of the gem dependency trees. You literally do > not know what gems to install.
I think what we were going for is that the gem installation process is *exactly* the same between MRI and JRuby. If you have to go through any other specific steps, then I would consider that a bug that we need to fix. The goal is that any tutorial that mentions getting started with DataMapper work exactly the same for JRuby users (and Windows users for that matter). Everything from the gem install commands, to the connection strings, to the model setup and code should be the same. We want to get to the point where platforms or OS is *not* mentioned anywhere in the docs (other than to say "it's all the same across all platforms"). Granted there is no support for native JRuby databases inside DataMapper, that would be really easy to fix should someone be interested in helping there. If those DBs support ANSI 92 SQL, then it should mostly be a matter of inheriting from the DataObjectsAdapter, and that's it. Take a look at the SQLite3, MySQL or PostgreSQL adapters for an example -- I think the largest of them is around a dozen lines long. You also need to look at the dm-migrations package and confirm that the DDL statements that are executed are supported by the DB. The main reason there's no support for the native JRuby DBs is because no one's asked for it. If someone is interested in setting one/all of them up please let me know. -- 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.
