Aldric Giacomoni wrote:

> You would most likely want to transfer all the data to a mySQL or 
> PostgreSQL database (possibly renaming the id fields to railsify the 
> whole thing) and then not touch the Sybase DB again.
> 
> Maybe get a Windows box or VM, just long enough to do what you want 
> (30-day trial for Windows) ?

Nice idea, but this is a legacy enterprise database used by other 
software, not so easy to abandon it.

My new plan (not really related to this thread, but perhaps useful for 
someone thinking about these things) is to write a web service in Java 
(there is already plenty of java code to talk to this db) that provides 
just the information needed by my ruby app (not actually the entirety of 
the database, not even close, just a few pieces of info, almost entirely 
read-only, for a few specific use cases) -- and just have the ruby app 
consume the web service instead.
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to 
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to