On Fri, May 3, 2013 at 8:37 AM, Marc <war...@gmail.com> wrote: So Tom: i can't use those methods Shawn pointed out? What I was hoping I > can do is override the code that builds the SQL query. > Further looking I think thats correct; as I did get a module working I > found and played with which uses those methods and they don't seem to > manipulate the query that is built by django, just the value passed. > > What isn't obvious in the Doc's Shawn is what is passed into and what is > expected to be returned. The docs are not clear at all about that at all. > > > > Sorry for the confusion. To be clear, I am suggesting that you make your own Field subclass, instead of using, for example, a CharField or TextField. The third link in that e-mail gave a working example of one. It should be very easy. It doesn't change the SQL at all -- it converts automatically between the plain text and encrypted value using those two functions named in the docs.
-- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
