When i worked with phptal+doctrine1 it turned out to be rather useful. It made sure that everything got loaded by a single query instead of lazy loading (which executes a query per every property) something behind the scenes.
While I agree that this kind of behavior is not the "correct" one, it is doctrine that acts "weird" not PHPTAL. Just my two cents :) On Mon, Nov 22, 2010 at 3:01 PM, Ivo Võsa <i...@insert.ee> wrote: > Kornel Lesiński wrote: > >> On 22 Nov 2010, at 12:35, Ivo Võsa wrote: >> >> >> >>> seams like today is feature request day :) so here goes mine. >>> >>> I'm using phptal with Doctrine ORM. >>> Unfortunately Doctrine and phtpal have different understanding about what >>> exactly isset means. >>> So every time i upgrade phptal i have to apply this little patch. >>> >>> >> >> How does isset behave in Doctrine? >> >> If $obj->foo exists, but is not loaded, does isset($obj->foo) return >> false? >> >> >> > yes it will return false, > and if you try to access it, it is loaded from database > > > _______________________________________________ > PHPTAL mailing list > PHPTAL@lists.motion-twin.com > http://lists.motion-twin.com/mailman/listinfo/phptal >
_______________________________________________ PHPTAL mailing list PHPTAL@lists.motion-twin.com http://lists.motion-twin.com/mailman/listinfo/phptal