I do kind of feel the same way about Perl. However, I've used it much more frequently than SQL. But I do find that it gets easier and easier to get back on the Perl horse each time I come back to it. I love using it.

I've read a book or two or three or four (ok, not cover to cover, admittedly) over the years on databases. For the kind of basic applications I write and with the dabbling I've done over the years, and with some help of existing websites, I can probably get by with the knowledge I have retained and create a decent schema; probably not the ideal one, but one that works good enough. Writing a perfect one can only come with lots and lots of practice.

Unfortunately, I have only limited time. So I'm just looking for some advice and learn from far more experienced programmers to help me to avoid unnecessary pain. I've found PerlMonks to be very beneficial in that respect. For example, I first learned about Moose last year here on PerlMonks and I am blown away by it. I love programming with it. So I greatly appreciate hearing these kinds of thoughts on best way to implement SQL. It all gives me food for thought. Thanks.