README.markdown in shuber-attr_encrypted-1.0.4 vs README.markdown in shuber-attr_encrypted-1.0.5

- old
+ new

@@ -1,11 +1,11 @@ attr\_encrypted =============== Generates attr\_accessors that encrypt and decrypt attributes transparently -Works with ANY class including ActiveRecord and DataMapper +Works with ANY class including ActiveRecord, DataMapper, and Sequel Installation ------------ @@ -259,22 +259,17 @@ Then you'll have these two class methods available for each attribute: `User.encrypt_email(email_to_encrypt)` and `User.decrypt_email(email_to_decrypt)`. This can be useful when you're using ActiveRecord (see below). -### DataMapper ### - -For your convenience, the `:encode` and `:marshal` options are set to true by default since you'll be storing everything in a database. - - ### ActiveRecord ### If you're using this gem with ActiveRecord, you get a few extra features: #### Default options #### -Just like the default options for DataMapper, the `:encode` and `:marshal` options are set to true by default since you'll be storing everything in a database. +For your convenience, the `:encode` and `:marshal` options are set to true by default since you'll be storing everything in a database. #### Dynamic find\_by\_ and scoped\_by\_ methods #### Let's say you'd like to encrypt your user's email addresses, but you also need a way for them to login. Simply set up your class like so: @@ -290,9 +285,14 @@ The call to `find_by_email_and_password` is intercepted and modified to `find_by_encrypted_email_and_encrypted_password('ENCRYPTED EMAIL', 'ENCRYPTED PASSWORD')`. The dynamic scope methods like `scoped_by_email_and_password` work the same way. NOTE: This only works if all records are encrypted with the same encryption key (per attribute). + + +### DataMapper and Sequel ### + +Just like the default options for ActiveRecord, the `:encode` and `:marshal` options are set to true by default since you'll be storing everything in a database. Contact ------- \ No newline at end of file