v3.3.1

Fix a bug in date serialization that could cause timezone shifting (#23).

Thanks to @mattnichols for hunting this down and finding a simple fix.

v3.3.0

Along with v3.2.2, this v3.3.0 contains a significant speed boost to #to_proto. Thanks to @brianstien and @abrandoned for working through this (#20, #21, #22).

v3.2.1

Remove use of deprecated Protobuf method (#19, @film42)

v3.2.0

Protobuf ActiveRecord now supports setting fields to nil using a special nullify field. Details can be found in the README (#16, #17). Thanks to @brianstien for doing the heavy lifting.

Additionally, there is now more control over which fields are automatically be serialized using the new :include option (closing #8).

v3.1.1

Ensure that mapping column names to Protobuf fields is threadsafe (#14, @abrandoned).

v3.1.0

Upgrade to Protobuf 3.0!

Protobuf ActiveRecord is now compatible with Protobuf 3.0 and uses the new message and enum APIs.

Also adds Rails 4.0 support for enabling query caching before requests and closing database connections after just like Rails does. This should ensure that Rails apps running an RPC server behave the same way as Rails apps running a Rack server.

v3.0.2

To support Rails 4 apps that use Mass-Assignment Security, Protobuf ActiveRecord now attempts to load the protected_attributes gem.

v3.0.1

Include fields that have attribute transformers

Previously, only attributes that didn't match fields, but had attribute transformers were included in attributes from proto. This omitted any fields that had transformers, but didn't have actual attributes (e.g. added via attr_accessor). Now any fields with attribute transformers are included.

Version 3.0!

Version 3.0 or Protobuf Active Record isn't a major departure from 2.1, and as such is (most) backwards compatible with it. The highlights of this release include:

• A completely refactored internal structure
• Automatic inclusion of the Protobuf Active Record into an Active Record object
• Compatibility with Rails 4.0