James, I assume you are talking about this approach:
class MyModel(models.Model) :
tags = TagField()
and not the one that is also suggested in the django-tagging README
that uses a custom save method along with a text field and a property.
i have verified that the 'tags' field in my objects is not updated
when i remove a tag through the Tag model's admin interface. the
Tag.objects.get_for_object() returns the correct list of tags but the
'tags' field is wrong.
would you point me to the code that you mentioned below?
thanks
konstantin
On May 11, 6:05 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 5/11/07, akonsu <[EMAIL PROTECTED]> wrote:
>
> > the tags_list field that you propose is an extra field that is stored
> > in the database. i want to avoid this because tags are stored in their
> > own tables and this field is only used for conveniency. the contents
> > of this field is not needed at all and it goes out of sync with the
> > tags if i remove tags through the Tags model's admin interface.
>
> I've done this (a 'tag_list' field on the model which updates in the
> background on save) on djangosnippets.org, and I thought Jonathan's
> app borrowed the update logic so that the tag field would stay in
> sync; a quick glance at the source seems to indicate this is the case.
> Could you verify that the TagField doesn't sync the list when you
> remove tags?
>
> --
> "Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
