At 00:46 07/01/2009, Lee Bolding wrote:
>However, it's recommended you don't - keep the table lean and mean to
>keep it fast, and also to maintain the standard behavior so that
>somebody other than yourself can easily maintain the code. There's a
>lot of noise about two separate tables, but realistically, you don't
>often need the data in sf_guard_user once a user has logged in.
Agreed. Though I got a bit annoyed with it yesterday when I needed to
retrieve some profile data and only knew the user ID, and had to join
in an extra table:
Doctrine_Query::create()->select('l.id, l.category_id, l.name,
p.first_name, p.email, u.id')->from('Listing l')->leftJoin('l.User
u')->leftJoin('u.Profile p')->where('l.id = ?',
$this->form->getValue('listing_id'))->execute()->getFirst();
Of course if I wasn't using Doctrine relations I could have gone
straight to the profile table and joined that ;)
Peter
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---
