I'm not in front of the dev machine, but I created the model in 0.95,
so maybe that's a dev feature. Or I may have had a typo in a model the
first time through- in fact I recall that I had a space in 'class Model
C', so if the 'name clash' detection requires all models to be created
at once, that'
On 11/4/06, yary <[EMAIL PROTECTED]> wrote:
>
> Russell Keith-Magee wrote:
> Django's model syntax already allows ambiguities. I just tried the
> above, and Django doesn't complain when you create the model, it does
Erm... I'd be interested to know how you tested this, because I get:
Error: Coul
Russell Keith-Magee wrote:
> On 11/3/06, yary <[EMAIL PROTECTED]> wrote:
> >
> > The idea here is that adding a 'realation_model' option to ManyToMany
>
> This idea has been suggested previously, and has been rejected
> previously - it has some problems when you hit queries.
>
> > All queries seem
On 11/3/06, yary <[EMAIL PROTECTED]> wrote:
>
> The idea here is that adding a 'realation_model' option to ManyToMany
This idea has been suggested previously, and has been rejected
previously - it has some problems when you hit queries.
> All queries seem pretty straightforward.
In your example
I cannot find any drawbacks in it right now ...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this grou
My previous brainstorm relied on magic- Models that look like fields?
auto-synthesized composite classes!? Django went through a magic
removal, adding magic won't fly.
An antidote to magic is explicitness. Let's try the previous example
from a different angle, spelling everything out.
class Repo
Well, it's nice altogether :)
I'll try to think about something ...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubsc
Wow, I hate being verbose and wrong at the same time in public. Take my
previous post with a grain of salt while I rethink it! sorry...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post t
Russell Keith-Magee wrote:
...
> That said, 'm2m with intermediate' is a relatively common use case, so
> if you have any neat ideas on how to represent such a structure, feel
> free to suggest them. The idea has been discussed before, but no
> obvious solution has emerged (the real sticking point
On 10/31/06, Vortexmind <[EMAIL PROTECTED]> wrote:
>
> Hi all
> I am currently developing a rather large data model, and I need to use
> Many-to-Many with Intermediate Table (as I need to stick some
> attributes within the association). I try to explain with the Django
> example about this issue:
Hello Malcom,
In cooking up my test I made some changes and did some rebuilding that
affected the database so I suspect that the "django_content_type"
table got out of sync (I really can't confirm this since I am now at
home)
I retried, as you suggested, with a clean database at home and there
On Fri, 2006-09-29 at 19:27 +, Paul Childs wrote:
> Could someone please tell me if this is an unfixed bug in Django 0.95.
> If it is I will submit a ticket.
>
> I created a many-to-many relationship using an intermediate table
> similar to
> http://www.djangoproject.com/documentation/models/
12 matches
Mail list logo
