Most modern DBMSs support automatic generation of primary (surrogate) keys. This affects a number of very common scenarios, which are addressed by CA Live API Creator as described below.
When inserting a row whose unique key is generated by the DBMS, the application needs to obtain the key in order to later retrieve or update the data. So, API Creator returns this in the update response.
When inserting a set of related rows (e.g., an Order Header and a set of Line Items), it is desirable this be done in a single transmission. Not only does this reduce latency, but it provides transaction bracketing. This is sometimes called a Cascade Add.
API Creator provides automated support for this common pattern. So, for example, it obtains the Order# from the DBMS for the inserted order, and "stamps" into each Line Item. Click here for more information.
Relational DBMSs require the introduction of a Junction (Link) table for many-to-many relationships, containing a Foreign Key of each of the related tables. See the deal / notes model shown here (schema available at bottom of this page).
Now consider inserting one (or several) Deal Notes with new notes, where we require:
You can define Custom Resources to address these requirements: