I found this answer and it sounds like almost exactly what I’m doing. I have heard mixed answers about whether or not datamapper can support SQL Server through dataobjects. Basically, we have an app that uses a consistently structured database, consistently named tables, etc in SQL Server. We’re making all kinds of tools and stuff that have to interact with it, some of them remotely and so I decided that we need to create some common, simple access point to do read/write operations on the SQL Server app since it’s API is all C# and other things I despise.
Now my question is if anyone has any examples or projects they know of where a ruby ORM can essentially create models for another application’s legacy database by defining the conventions of each model’s pkeys, fkeys, table names, etc. Sequel is the only ORM I’ve used with SQL Server but never to do anything quite like this. Any suggestions?
Sequel doesn’t automatically create models, but you could write an extension that took the output of Sequel::Database#tables and Sequel::Database#schema (for each table), and did some analysis of the keys and table names to guess at associations. The reason Sequel doesn’t do this by default is that it isn’t possible to do correctly in all cases. But if your database always follows certain conventions, you could certainly get it to work.