On 6/2/07, Sean <[EMAIL PROTECTED]> wrote: > > I have gotten the encryption and decryption code down and I have been > able to override the appropriate functions so that the data is > encrypted when it is saved to the database. Unfortunately I have not > been able to figure out what function to override to decrypt the data > when it is loaded from the database.
As you noted, modifying data going into the database is easy; modifying data coming back out is not. There isn't any framework at present for supporting data manipulation of this type. The Django GIS branch has been making some suggestions on how to integrate this functionality; there has been some separate discussions about "datatype coercion" which follow a similar theme. If you have any use cases or suggestions, feel free to join into the discussions on django-developers. > Additionally I have a strange problem where any time I include this > custom field in a model, that model no longer appears in the Django > admin. There doesn't seem to be any errors in the field/model since I > can use it with out problems from the shell. I haven't looked at this problem specifically, but I'd hazard a guess that because the field isn't providing any hints on how to be displayed in Admin, it throws an exception somewhere, which causes Admin to ignore the model. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
