sporty wrote: Problem with stuff like that, is your objects and your tables don't always conincide.
sporty, have you ever looked at Pixie? I don't know what you mean by "objects and tables don't always coincide". The Pixie philosophy is simple: we want to persist objects. And that's all it does. There's no complicated framework or worrying about how the tables relate. You store objects. You retrieve objects. That's it.
You also wrote "interface represents your database model". The underlying database is completely independant of the object interface and, in fact, that was one of the design goals. Pixie doesn't care what your interface is. However, I could be misunderstanding what your concerns are, so if you care to elaborate, I'd love to hear what you have to say.
Disclaimer: I've not used Pixie either. I toss it out there because Piers Cawley (who's done a lot of work on Pixie) recommended it and I have a lot of respect for him.
Cheers,
Ovid
New address of my CGI Course.
In reply to Re(3): Mixing Mysql and Perl
by Ovid
in thread Mixing Mysql and Perl
by SavannahLion
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |