On Saturday 14 Jan 2006 7:01 pm, ChaosKCW wrote:
> reporter = article.get_reporter()
>
> Is there some reason this isnt dont automactically for you on as
> follows on attr access:
>
> reporter = article.reporter
that is the id which is stored - take a look at the table structure
created in the
Mostly I agree with that statement. If you going to use the attribute,
then you need to use it. You have to take a hit at some point.
I rember using a world class ORM tool in jaav that allowed join fetches
for first elvel attributes for perfroamnce. While I dont expect that of
this api for some
That smells too much of premature optimisation ;-) If you know your
model slightly, you know when a database hit happens (and it might be
unavoidable anyway, so why worry?).
El sáb, 14-01-2006 a las 13:51 +, Luke Plant escribió:
> One reason for the way it is at the moment is it's easy to see
Thanks,
Luke Plant wrote:
> On Sat, 14 Jan 2006 13:31:52 - ChaosKCW wrote:
>
> > In the Reporter/Article example on the Django site, to get the
> > reporter of an article requires you to call the a method:
> >
> > reporter = article.get_reporter()
> >
> > Is there some reason this isnt don
On Sat, 14 Jan 2006 13:31:52 - ChaosKCW wrote:
> In the Reporter/Article example on the Django site, to get the
> reporter of an article requires you to call the a method:
>
> reporter = article.get_reporter()
>
> Is there some reason this isnt dont automactically for you on as
> follows
5 matches
Mail list logo
