Makoto Inada wrote:
> I know this is not a straight answer, but you may want to check
> ActiveRecord in RoR.  It works standalone nicely outside of the framework.

Probably a good idea, but unfortunately I cannot abstract the Database 
too much.
1.) I didn't develop the database myself, and working with it from a 
pure SQL POV is a pain in the neck. I can't imagine the problems I'm 
going to have to wrestle
2.) Those who did have no real clue what the benefits of an SQL Database 
are (a VARCHAR field is set as an INDEX, for example, I have yet to see 
a FOREIGN KEY, and the column itemid in one table could be named item_id 
in the next, while containing the same data, and so on..).

And thirdly, but more importantly, I want to bring my SQL skills up to 
speed, too. I don't want to handle just the usual suspects of SQL 
statements, but broaden my skillset a little more towards DBA.

And I really, really cannot add another thing to my "things to learn to 
do a good job of it" list. Before I tackle *anything* related to Rails, 
I want to write fluent and *good* Ruby first.


-- 
Phillip "CynicalRyan" Gawlowski

Rule of Open-Source Programming #34:

Every successful project will eventually spawn a sub-project