Encrypted fields are constantly being persisted to the Database even when they aren't being modified.

[jayesbe]

Anytime I perform an $em->flush(); An Entity that was loaded which contains encrypted fields will show up as an UPDATE statement in the log. There are no changes to the entity. The fields aren't even used. The UPDATE should not occur.

Aside from this, My understanding of the code is that the values are decrypted as soon as the entity is loaded.. shouldn't they only be decrypted when some encrypted field is retrieved from the Entity ?

[jayesbe]

Looks like someone fixed this

bouke-nederstigt@3c1255b

[numediaweb]

@jayesbe
Is this still an issue? or is it already fixed/merged?

[jayesbe]

@numediaweb ive moved on to a fork of this project. https://github.com/michaeldegroot/DoctrineEncryptBundle

[Henridv]

Looks like someone fixed this

bouke-nederstigt@3c1255b

This change doesn't fix this issue.

From what I see the fork also doesn't fix this? @jayesbe

[jayesbe]

@Henridv I am using the degroot fork however I do have a fork of my own with the fix merged.

absolute-quantum/DoctrineEncryptBundle@master...Indinuity:degroot

[Henridv]

@jayesbe
Thanks!

However, your fix only reduces the encrypt/decrypt operations. All entities with encrypted properties fetched from the database will be marked as 'dirty' in the entity manager.
As such, every flush() will cause all entities to be written back to the database.

[jayesbe]

@Henridv interesting.. What happens if you flush() only the entities you are modifying?

I don't know when I'll have time to look into it.. if you get a chance to look into it further or come across a better fix let me know.

[jriboux]

@jayesbe, @Henridv I think I found a workaround using the "deferred explicit" tracking policy (See doctrine documentation).

Setting deffered explicit tracking policy to all entities containing encrypted fields will prevent them from being automatically persisted on flush. They will be persisted only if persist() is explicitely called on each instance you want to save in DB.

[jayesbe]

@jriboux are you working on an PR ?