On Wed, 2007-05-16 at 09:42 -0700, [EMAIL PROTECTED] wrote: > *sigh* posted to quickly. The solution was to define get_internal_type > to return TextField.__name__ > > On May 16, 12:40 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > Turns out I decided to go with the Field class since I'll be needing > > them in a few different models. The issue I'm running into now is that > > the new field name isn't defined in the data_types list (from db/ > > backends/*/creation.py). > > > > Obviously I can just add an entry for the backend I'm using, but that > > seems wrong. I inherit from TextField, is there anyway to tell it to > > just use that type?
Remember how I said there were a few pieces of machinery missing to make subclassing Fields easy? You just found one of them. :-) Yes, it has a solution, but it should be automatic in a perfect solution. Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
