Sorry for the spam here, but I came across something going through the
code switching process that I think may actually call for more than
the standard MtM Field.
What happens if you need to add additional fields to your join table?
For example, let's say you had an employees table and a
Oh, wait, duh, that's what the Many-to-Many relationship is.
Sorry about that. I feel rather dumb now.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
On Mar 26, 4:40 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> What is the use-case for something like this in Django? The only times
> we do SQL inserts are when we're saving a model instance or updating a
> many-to-many relation. I can't see either of those really needing this
> type of
On Wed, 2008-03-26 at 14:36 -0700, Brian P Armstrong wrote:
> Hi,
>
> I was working on moving an old site from php to django and found that
> I was using INSERT...SELECT... queries in a couple places. The point
> of these queries is to take a group of rows using the SELECT subquery
> and
Hi,
I was working on moving an old site from php to django and found that
I was using INSERT...SELECT... queries in a couple places. The point
of these queries is to take a group of rows using the SELECT subquery
and insert them all at once without having to iterate over them in
your code.
5 matches
Mail list logo
