On Tue, 2008-12-16 at 12:08 -0600, David Cramer wrote: > I should also note, that these changes, could possibly be carried over > into Model Field's. As IIRC they were suffering from some of the same > problems.
Again, specifics are important. Pretty much all existing model fields wrap base database and Python types and don't need any of the extra machinery from SubfieldBase. Please provide more details. I have another response to your other post, since I'm unconvinced those hooks are really needed (the database loading thing is called to_python() already -- adding an extra one shouldn't be necessary). But I don't have time to rewrite the code sample yet and that will be a necessary part of the explanation. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
