Never mind, I see it's to do with database backends.
On Dec 11, 10:34 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> OK, well now, for some reason whenever I use a custom field Django
> just ignores it when running syncdb. If I ask it for the raw SQL
> output I can see that the field is being omitted entirely. Even if I
> do something simple like:
>
> class TestField(models.TextField):
> pass
>
> Does anyone know what I am doing wrong?
>
> On Dec 11, 9:04 pm, "Marty Alchin" <[EMAIL PROTECTED]> wrote:
>
> > On Dec 11, 2007 3:42 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> > > When I try to run syncdb on a model which uses the PickledObjectField
> > > (see my sample model athttp://dpaste.com/hold/27713/), I get this
> > > traceback:-
>
> > Your problem is that you're importing the PickledObjectField into your
> > class's namespace. So when Django processes your form definition, it's
> > actually getting two attributes:
>
> > * lookups (instantiated, which will work fine)
> > * PickledObjectField (uninstantiated, which will cause errors)
>
> > Move the import statement to the top of your models.py file, where it
> > belongs, and you should find that the error goes away.
>
> > There are no doubt other things you'll run into, but I'll at least
> > give you a chance to work them out on your own. :)
>
> > -Gul
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
