JSON parameter binding of Map fields is no longer consistent and causing extra updates

[tanadeau]

After upgrading to 2.20.0 from 2.19.2, the binding for JSON parameters is no longer consistent when used with Map fields in entities. This is causing an unnecessary update after every insert and also extraneous updates for other entities in the session.

For example, in the insert operation the parameter is bound as:

2022-11-30 12:50:22.255 [accountName=admin] TRACE 55394 --- [nio-8080-exec-7] o.h.type.descriptor.sql.BasicBinder      : binding parameter [18] as [OTHER] - [{9afc49ea-d869-4e50-ab1c-05af93dfaf8e=[{creatorId=1ed70d69-2a4b-6fe0-bd04-7effac365278, createdAt=2022-11-30T12:50:22.142682-05:00, lastModifiedById=1ed70d69-2a4b-6fe0-bd04-7effac365278, lastModifiedAt=2022-11-30T12:50:22.142682-05:00, value={repeatableSectionInstanceId=null, autoPopulated=false, value=12616541, fieldType=TEXT}}]}]

However, in the update that immediately follows it, the JSON column is updated with a parameter bound as:

2022-11-30 12:50:22.271 [accountName=admin] TRACE 55394 --- [nio-8080-exec-7] o.h.type.descriptor.sql.BasicBinder      : binding parameter [1] as [OTHER] - [{9afc49ea-d869-4e50-ab1c-05af93dfaf8e=[ReportEntityValueEntry(creatorId=1ed70d69-2a4b-6fe0-bd04-7effac365278, createdAt=2022-11-30T12:50:22.142682-05:00, lastModifiedById=1ed70d69-2a4b-6fe0-bd04-7effac365278, lastModifiedAt=2022-11-30T12:50:22.142682-05:00, value=ReportEntityValueText(repeatableSectionInstanceId=null, autoPopulated=false, value=12616541))]}]

I believe this may be due to the changes for #494.

[vladmihalcea]

A replicating test case id needed for this use case. You can use this test case as a reference for asserting the number of statements that get executed.

[vladmihalcea]

No replicating test case was provided. I'll reopen it once an integration test is created to prove the issue.