2. May 2016
With great pleasure Dataloy presents API 3.0
Highlights of this Release:
Highlights of Dataloy API 3.0
Ability to Update Sub-Objects and Lists and Update in a Single Transaction
API 3.0 introduces the ability for a user to input/update/replace sub-objects and lists and to update all in a single transaction. It is also possible to update sub-objects (for example, voyage on voyage header resource) by sending in code/id.
As PO I want to have the Cargo business logic as is in Kara implemented in DLP correcly
As PO I want to have the Cargo business logic as is in Kara implemented in DLP correcly
As architect I would want to have a automatic mechanism to invoke business logic during POST and PUT methods
As API user, I want to data changed outside API do be refreshed, so that I can trust data received by the API
As API user, I want to data changed outside API do be refreshed, so that I can trust data received by the API
Every time there is some change in the DB a trigger/s will insert a row in a new table, the table will have three columns:
- Object name (the corresponding DLP object name of the table that has been changed)
- primary key value (the key of the row that has been changed)
- creation time stamp (the time stamp of the row creation)
The first two columns will be the primary key of the table.
A job that runs inside DLP will constantly see if there are rows in the table and if yes will refresh the corresponding cayenne object and delete the row from the table.