*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? > > --Lucki > > On May 16, 10:54 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > Thank you both for your help. I really should have thought of the > > proxy attribute myself. I use Property objects all over the place > > already. I'll probably go with that solution since I'm a bit time > > crunched and can do that one quickly. Though I think the Field class > > would be the 'better' solution. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
