On Wed, 2007-11-28 at 12:33 -0800, Doug B wrote: > Is there a way to make custom model field that works normally except > for database interaction where it is ignored. In looking at the > source it doesn't seem possible but I thought it couldn't hurt to ask.
No. You're going to really have to do this yourself. Pretty much by definition, a django.db.models.field.* class is something that is persisted to the database. Everything else would be just a normal Python property. You could take inspiration from GenericRelation fields, although (a) there's some risk that your head will explode when reading the code because it's a little scary and (b) they don't work in admin yet, so your primary use-case doesn't have an example to copy. My understanding is that the latter case is because is just isn't done yet (but is in progress), rather than because it's fundamentally hard. Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
