Per-Olof H. wrote:
David M. wrote:
I looked at doing this myself as my first Rails project, but quickly
decided it was too much to bite off. —
Bottom line: Rails has a definite sweet spot in terms of app
architecture, and integrating with large legacy Oracle databases is
quite a way from that sweet spot!
Thanks for your lengthy and insightfull answer. I understand - what you
say it confirms what I have senced when reading RoR websites and
following forum discussions.
I will do as you suggest, start with MySQL for learning and training,
then do a simple solution with Postgres, and then see where I go from
there. Maybe it is easier to port our application from Oracle to
Postgres than getting RoR to work with our Oracle database. We have only
some 50 views, procedures, triggers.
I too am relatively new to RoR and climbing that learning curve with a
legacy Oracle database strapped to my back.
I agree with Dave, it’s always going to help to get familiar with RoR by
trying out a few simple examples. I’ve messed around with a few MySQL
legacy databases, tried out some basic tutorials and all of that has
helped me get up to speed with RoR. I now recognise a lot of the common
errors which should make any new oracle-related errors easier to spot.
My next step on the ladder involves working with a large legacy oracle
database. So far I’ve defined all the relationships between tables and
have a web app that just let’s me browse and search the legacy database.
I’ve not yet got around to messing with updates, deletes, stored
procedures, sequences and have no doubts that I’ll encounter challenges
when doing so, but I’ve not encountered any Oracle-specific problems so
If you want to eventually use Rails with your legacy Oracle database,
then why not do your experimenting with a test Oracle database. Create a
few simple tables with a variety of field types, set your foreign keys,
create views, triggers and everything else that your legacy database
has. Then use your test database in your experiment. That way you’ll
have the proof that it can be done when you’re finished experimenting.
If you hit a brick wall then there’ll be no harm done and I bet there’s
more than you, Dave and I on this mailing list developing oracle-backed
apps who would be willing to help out.
Rails abstracts a lot of the SQL to keep things simple for us, but bear
in mind you can still write sql to solve some of the problems you might
encounter. I’ve had to do this with some complex queries in order to
improve performance but I can see it being a useful way of overcoming
other problems too. If the worst comes to the worst you may be able to
replicate the function of your stored procedures in rails too.