aight to the db.
>
> I can see some issues with this coming up, especially if you're doing
> deletes with django's raw sql capability. But that should never happen,
> you should do a select then iterate and delete.
>
> On Saturday, June 23, 2018 at 9:28:15 AM UTC-4
OK. So it's by design.
So during development I can't go straight to the database and delete a
"Group" quickly due to an error I made. I'd have to set up tests to deal
with it at an application level.
No probs though. I'm just happy I know it can't be done and not that it's a
bug I'd have to wa
00:56:36 CEST James Bellaby wrote:
>
>
>
> > However when looking are the SQL in Postgresql it's created the
> Membership
>
> > table constraint for the Group id with "ON DELETE NO ACTION"
>
> >
>
> > CONSTRAINT groups_membershi
I'm having a little trouble with my "through" table. I've set the modal to
have two Foreign Key fields. Ex. below:
class Person(models.Model):
title = models.CharField(max_length=255)
class Group(models.Model):
title = models.CharField(max_length=255)
members= models.ManyToManyField
4 matches
Mail list logo
