> Oh, I see where you're going with it. Just hide the interface from the > user. That's a great idea, I still need a way though to enforce it so > that carefully crafted POST requests don't allow unauthorized users > from breaking things.
That's true, maybe using the custom manipulator would handle that, but I'm not so sure. Possible a combination of the two methods would work, either save and template or manipulator and template. Either method works, more just style then anything else. > > That was my first pass. I subclassed models.IntegerField and overroad > get_manipulator_field_objs, and return my custom Form. However, when > running syncdb I still got a KeyError. > > I think that there is a dict somewhere that maps models to their sql > implementation and that my model doesn't exist in that dict, hence a > KeyError. But that's really just a guess. I'd love to hear from an > authority about where the sql structure of a model is defined. When I get a moment later this evening, I'll dive into the DB code and see what else I can find. From the top of my head, I don't think there is anything, but I might be wrong...when I've been exploring the DB code I haven't looked for anything along those lines. Maybe pastebin the code and the trace and I can offer some more help. Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
