Update docs and changelog

activerecord/CHANGELOG.md

@@ -1,3 +1,13 @@
+*   Deserialize database values before decryption
+
+    PostgreSQL binary values (`ActiveRecord::ConnectionAdapters::PostgreSQL::OID::Bytea)
+    need to be deserialized before they are decrypted.
+
+    Additionally ensure that the order of serialization/deserialization is consistent
+    for `serialize :foo` and `encrypts :foo` whichever order they are declared in.
+
+    *Donal McBreen*
+
 *   Infer default `:inverse_of` option for `delegated_type` definitions.
 
     ```ruby

guides/source/active_record_encryption.md

@@ -147,21 +147,7 @@ To encrypt Action Text fixtures, you should place them in `fixtures/action_text/
 
 `active_record.encryption` will serialize values using the underlying type before encrypting them, but, unless using a custom `message_serializer`, *they must be serializable as strings*. Structured types like `serialized` are supported out of the box.
 
-If you need to support a custom type, the recommended way is using a [serialized attribute](https://api.rubyonrails.org/classes/ActiveRecord/AttributeMethods/Serialization/ClassMethods.html). The declaration of the serialized attribute should go **before** the encryption declaration:
-
-```ruby
-# CORRECT
-class Article < ApplicationRecord
-  serialize :title, type: Title
-  encrypts :title
-end
-
-# INCORRECT
-class Article < ApplicationRecord
-  encrypts :title
-  serialize :title, type: Title
-end
-```
+If you need to support a custom type, the recommended way is using a [serialized attribute](https://api.rubyonrails.org/classes/ActiveRecord/AttributeMethods/Serialization/ClassMethods.html).
 
 ### Ignoring Case