On Tue, Jul 8, 2008 at 9:57 PM, ristretto.rb <[EMAIL PROTECTED]> wrote:
>
> More details. I'm using MySQL at the moment (but with a plan to move
> to Postgresql.) The association table has a number of rows loaded
> through these models, but not through my Django app directly. I used
> the Model classes in a script to pre load a bunch of data. Could this
> be the problem?
>
> On Jul 9, 1:28 pm, ristretto.rb <[EMAIL PROTECTED]> wrote:
> > OK, I took core=True off, and added it to the reference_no field. The
> > problem seems to go away for the case when no there are no
> > pre-existing joins. Clearly, I don't understand what core is for.
> > I'll read the docs again, and see if it makes sense.
> >
> > However, it still errors with
> >
> > {'jointable.0.id': [u'Join Table record with this ID already exists.']}
> >
> > when I tried to save a LeftSide records with existing associations.
> >
> > thanks for any and all help.
> >
>
I have no idea what is going on, but a ticket was recently (4 hours ago)
opened reporting the same error message for inline-edited objects:
http://code.djangoproject.com/ticket/7682
It seems like some code is thinking records are supposed to be new and
checking for primary key uniqueness when in fact it is existing records that
are being updated. This might be a recently introduced bug, it's a little
curious to have two people reporting the same (not common) error message
suddenly so close together.
What version are you running?
Karen
>
> >
> > On Wed, Jul 9, 2008 at 1:09 PM, ristretto. rb <[EMAIL PROTECTED]>
> wrote:
> > > Hello, I'm stuck. Any help will be much appreciated.
> >
> > > I followed
> > >http://www.djangoproject.com/documentation/models/m2m_intermediary/tomake
> > > a
> > > Many-to-many relationship via an intermediary table.
> >
> > > class LeftSide(models.Model):
> > > :
> >
> > > class RightSide(models.Model):
> > > :
> >
> > > class JoinTable(models.Model):
> > > leftSide = models.ForeignKey(LeftSide,
> > > edit_inline=models.TABULAR,
> > > num_in_admin=3, core=True)
> > > rightSide = models.ForeignKey(RightSide,
> > > edit_inline=models.TABULAR,
> > > num_in_admin=3,core=True)
> > > reference_no = models.CharField(max_length=10, null=True,
> blank=True)
> >
> > > I can load the LeftSide in the admin, and choose to Change a record. I
> get
> > > 3 RightSide menu groups at the bottom. I can choose a RightSide to set
> as a
> > > join. When I choose Save (any of the 3 save variations on the page)
> nothing
> > > is saved.
> >
> > > There are two cases.
> >
> > > 1) If the are already records in the join table for that LeftSide,
> then I
> > > get an error when I save. {'jointable.0.id': [u'Join Table record
> with this
> > > ID already exists.']} I didn't actually make any changes to that
> > > association, so I don't know why it would complain.
> >
> > > 2) If there are no join table records associated with the LeftSide,
> then
> > > there is no error, but nothing is saved.
> >
> > > Am I doing something totally wrong here? Or is this a bug in the Admin
> > > system?
> >
>
--~--~---------~--~----~------------~-------~--~----~
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 group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
