On Dec 21, 7:46 pm, tim <[email protected]> wrote: > I am about the start a project to rewrite some existing ruby code. > > The existing code uses ruby and dbi to talk to sql server 2005 using > ADO (and in a couple of cases ODBC). This seems to work OK. > > As long as I am rewriting this I thought I would switch to sequel and > jruby. > > Before I go down this rabbit hole I would like to get the opinion of > the group on whether this is a bad idea or not. Is the combination of > jruby, sequel and sql server viable or not?
Honestly, I'm not sure. It shouldn't be hard to try a short proof of concept to see what works and what doesn't. Try running the integration tests that come with sequel using a test database on the SQL Server 2005 server. The one problem you may to run into is getting insert to return the primary key of the inserted records, but that is likely to be an issue no matter if you use ADO, ODBC, or JDBC. Jeremy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
