I don't see how this is even possible, how are you supposed to store this data encrypted and still be able to search it? Are we supposed to unencrypt the entire database table each time we want to search the data that's there? What about caching? Can you cache stuff unencrypted? This is crazy. That said, if you do not need to "search" it, you can use filter_in and filter_out http://www.web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#filter_in-and-filter_out
Note that I do not find anything in the GDPR that demands that all of this data be encrypted at the database level or at all times. Encryption is just one of the measures you can take to protect personal data. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
