Null value in (non-attr-encrypted) column when upgrading to 4.0.0

[prognostikos]

We attempted to upgrade attr_encrypted from 3.1.0 to 4.0.0 but ran into a test failure.

We have a model that has an attr_encrypted column as well as a uuid that is generated on insert by the database. After the upgrade, the uuid column of the model was nil in ruby code, though it was generated properly in the database row. Adding a call to reload before accessing the uuid column fixed the issue.

Rake about says:

Rails version             6.1.7.3
Ruby version              ruby 3.1.3p185 (2022-11-24 revision 1a6b16756e) [arm64-darwin21]
RubyGems version          3.3.26
Rack version              2.2.6.4

[joshbranham]

Does this only fail in tests? Can you provide a reproduction example?

[prognostikos]

It failed in live code as well, the tests were just what caught it. I will see if I can provide a repro, unfortunately the test is a feature test with a lot of state so it will take some effort to make a simple example.

…

On Thu, Apr 20, 2023 at 6:30 PM Josh Branham ***@***.***> wrote: Does this only fail in tests? Can you provide a reproduction example? — Reply to this email directly, view it on GitHub <#438 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAD5ZNWNU2PP753K77WUPKTXCFQDRANCNFSM6AAAAAAW575W4U> . You are receiving this because you authored the thread.Message ID: ***@***.***>