I have custom save methods like:

class Issue(models.Model):
    title = models.CharField(maxlength=150)
    parent = models.ForeignKey('self',
                               null = True,
                               blank = True)
    industries = models.ManyToManyField(Industry,
                                        null = True,
                                        blank = True)
    slug = models.SlugField(maxlength = 100,
                            editable = False)

    def save(self):
        slug = self.title
        parent = self.parent
        while parent:
            slug = '%s %s' % (parent, slug)
            parent = parent.parent
        self.slug = slugify(slug)
        super(Issue, self).save()
        for child in Issue.objects.filter(parent = self):
            child.save()

Using the admin, I was able to add objects, so I think the custom
save() works fine. Can loaddata be misinterpreting the custom save()?

For the paths suggestion, I drop the tables and run syncdb. The tables
are created, but they are not populated. Syncdb sees correctly which
db I meant while creating tables.


In my previous post, I have omitted custom save() methods in the
models for simplicity but I see it can be critical, so here is the
full model:
http://dpaste.com/hold/15751/



On 1 Ağustos, 16:14, omat <[EMAIL PROTECTED]> wrote:
> Thanks for the reply Russ...
>
> The models are here:http://dpaste.com/hold/15746/
>
> The dump in json format is here:http://dpaste.com/hold/15747/
>
> On 1 Ağustos, 15:52, "Russell Keith-Magee" <[EMAIL PROTECTED]>
> wrote:
>
> > On 8/1/07, omat <[EMAIL PROTECTED]> wrote:
>
> > > Installed 34 object(s) from 1 fixture(s)
>
> > If this message is getting printed, then the fixture is getting loaded
> > _somewhere_, save() has been called on 34 object instances, and the
> > transaction has been successfully committed.
>
> > The only way I can think that the data would go missing was if it was
> > loaded into a different database. However, I can't think of any
> > obvious way that you could do this.
>
> > Another possibility is that the loaddata success is getting
> > misreported somehow. If you forward your model and fixture I'll try it
> > at my end and see if I can replicate the problem.
>
> > Yours,
> > Russ Magee %-)


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to