Re: Shouldn't get_profile() create the profile object?

On Thu, Jan 8, 2009 at 12:26 AM, Malcolm Tredinnick wrote: > > On Wed, 2009-01-07 at 22:50 -0200, Alvaro Mouriño wrote: >> I find myself checking for the existence of the profile object for the >> user everytime I call the get_profile function or making sure that it >>

Re: Shouldn't get_profile() create the profile object?

On Thu, 2009-01-08 at 09:56 +0100, Thomas Guettler wrote: > Alvaro Mouriño schrieb: > > I find myself checking for the existence of the profile object for the > > user everytime I call the get_profile function or making sure that it > > gets created with every user. > > > > > Since a lot of

Re: Shouldn't get_profile() create the profile object?

Alvaro Mouriño schrieb: > I find myself checking for the existence of the profile object for the > user everytime I call the get_profile function or making sure that it > gets created with every user. > > Since a lot of users have this question/problem I added a patch to the documentation:

Re: Shouldn't get_profile() create the profile object?

On Wed, 2009-01-07 at 22:50 -0200, Alvaro Mouriño wrote: > I find myself checking for the existence of the profile object for the > user everytime I call the get_profile function or making sure that it > gets created with every user. > > Is there a reason for this? Shouldn't the framework assure

Shouldn't get_profile() create the profile object?

I find myself checking for the existence of the profile object for the user everytime I call the get_profile function or making sure that it gets created with every user. Is there a reason for this? Shouldn't the framework assure me that I will get a profile whenever I call get_profile()? Even