Hi Russ,
As Jeff has already said, this decision is understandable. I had
found myself up against a wall when I created the solution... I
figured it might be useful for other developers, but won't push for
its inclusion in the base distribution.
Further comments are below.
On Mar 11, 6:20 pm,
On Mar 11, 6:20 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> If you have two models in different apps that are
> self referential, then you don't really have two
> apps - you have one app (or, two apps that are so
> closely related that they probably should be one
> app)
Russ,
I unders
On 3/10/07, Benjamin Slavin <[EMAIL PROTECTED]> wrote:
> Howdy folks,
>
> I just created ticket #3688 [0]. It introduces a change we've been using
> internally for a few weeks and I thought might be useful to other users.
Thanks for the contribution, Benjamin, but the existing behaviour (or
lack
On 3/9/07, David Danier <[EMAIL PROTECTED]> wrote:
>
> I don't see the real advantage over:
> 8<-
> from foo.accounts.models import User
> [...]
> models.ForeignKey(User)
> ->8
>
Check out the t
> This patch allows dotted notation ('app_name.model_name')... the same as
> used by Django's "get_model". So, for example:
> models.ForeignKey('accounts.User')
I don't see the real advantage over:
8<-
from foo.accounts.models import User
[...]
+1
Without commenting on the patch itself, I'd like to say it addresses
an issue I've had with model relationships. Thanks for posting this
ticket!
--
Jeff Bauer
Rubicon, Inc.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goo
Howdy folks,
I just created ticket #3688 [0]. It introduces a change we've been using
internally for a few weeks and I thought might be useful to other users.
Currently ForeignKey references can be to:
* A class defined either in the current models.py or imported (via 'import')
from another mode
