v9.0_2013-07-03/LGPL Development Only (built 2013-07-03)
I have ListGrid showing records from a legacy database. The tables in this legacy database have composite primary keys. From the front end the user can edit these composite primary keys. The situation is that whenever the user edits the composite primary key, a new record is shown in the ListGrid
with the previous record still there. This contrasts to the database side of things where the update request is handled without error and results in the same row now having a new composite primary key.
This display of old record seems to be a caching issue as ListGrid interprets the JSON response with a different composite primary key as a new record. Whats the best way to solve this issue.
I have ListGrid showing records from a legacy database. The tables in this legacy database have composite primary keys. From the front end the user can edit these composite primary keys. The situation is that whenever the user edits the composite primary key, a new record is shown in the ListGrid
with the previous record still there. This contrasts to the database side of things where the update request is handled without error and results in the same row now having a new composite primary key.
This display of old record seems to be a caching issue as ListGrid interprets the JSON response with a different composite primary key as a new record. Whats the best way to solve this issue.