Nathan Lane wrote:
Thanks for the explanation. I've been looking into Active Record for
PHP, thinking that maybe it would be a worthwhile investment. The only
thing is that after having briefy used Active Record in Ruby, I feel
kind of constricted by naming conventions - plurality for tables,
singularity for rows, and I gues I just don't understand it very well,
but I don't like that either. So is ORM more flexible? You say it
"maps" to database entities, does that mean that my tables can have any naming
convention I decide
on? Also, I guess what I'm really looking for is more of a .Net Linq solution for PHP, but still not exactly that. I just want a decent data
abstraction layer.
Nathan
I guess you could say that Outlet is similar to "Linq to Entities",
without the actual compiler-checked linq language (just the mapping code).
Outlet let's you name the tables and fields however you want. I'm also
working to allow defining entities that map to more than one table, and
entity properties that map to more than one field. The original design
allows for these enhancements, I just need the time to program them. The
main objective I was shooting for at the beginning of this project was
"clean" entities, which I don't think any other php ORM (this includes
active record implementations) gives you right now.
Alvaro
_______________________________________________
UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net
