Pixie basically says "forget about a framework, I just want to store an object." And that's what it does. Thus, you don't need to worry about designing the database. Simply use your objects and store and retrieve them as needed. No muss, no fuss. I've not used it, but it sounds very interesting.Problem with stuff like that, is your objects and your tables don't always conincide. Most of the time they don't. For instance, say you have 4 or 5 types of users that all inherit from the same base object. Their base data may be the same, but the extended part of it may store differently. You wouldn't store ALL the data in one table and you may not wish to have certain columns laying about if your user types are grossly different.
Pixie may be great for simple things, but if things get complex, modules like pixie would lead into an "interface represents your database model" which is a pitfall.
In reply to Re: Re: Mixing Mysql and Perl
by exussum0
in thread Mixing Mysql and Perl
by SavannahLion
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |