apinstein

Heh no problem. I'll cc the list for you.

So basically propel creates an object to represent each table in a =20
DB. Foreign key relationships are maintained, and the propel objects =20
cache the results.

So, in a simple scenario with "Account" and "Transactions", your =20
"Account" object keeps an internal "collection" of transactions and =20
each "transaction" keeps an internal reference to its "Account". =20
There's the circular reference.

So, if you could explain your idea (a) as a solution to this =20
architecture, that'd be great.

Also, why don't you describe (b) anyway just for fun

Alan


--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php