Page History
...
| Note |
|---|
See also the Database Manager's getEditedRecords and the JSRecord's getChangedData methods. |
Saving Data Changes
A developer can programmatically issue a save event, causing the contents of the In-Memory transaction to be automatically translated into instructions to insert/update database tables. A developer can optionally invoke a save event for a specific record only, leaving the rest of the transaction unaffected.
If for some reason one or more records were unable to be saved (i.e. due to a back-end database violation, etc.), the transaction will also keep track of Failed Records and their associated errors.
| Note |
|---|
See also the Database Manager's saveData and getFailedRecords methods, as well as the exception property of the JSRecord |
Rolling Back Data Changes
A developer can programmatically issue a command to rollback the contents of the entire In-Memory transaction, causing newly created records to be removed and modified records to be reverted to their state prior to the start of the In-Memory transaction. The developer can optionally choose to rollback changes for a specific record, leaving the rest of the transaction unaffected.
Note
See also the Database Manager's rollbackEditedRecords method, as well as the rollbackChanges method of the JSRecord.
Note
What about Deleting Records?
It is important to note that record deletes are not part of the In-Memory transaction. When a record is deleted, the instructions are sent to the database immediately and the delete cannot be rolled back.
Note
See also the deleteRecord method of the JSFoundset.
Note
The Servoy Foundset
The Servoy Foundset is a developer's window into Servoy's Data Binding layer. A single foundset always maps to a single database table (or view) and is responsible for reading from and writing to that table. From the user interface, a foundset controls which records are loaded and displayed, as well as how records are created, edited and deleted. From the developer's perspective, a foundset is a programmable object with specific behaviors and run-time properties that provide a high-level abstraction to facilitate low-level data operations.
| Note |
|---|
For all programming reference information, see the JSFoundset API documention in the reference guide. |
Forms Bound to a Foundset
...
| Note |
|---|
While a form is always bound to a foundset, a foundset may be used by 0 zero or more forms. Foundsets can be created and used by a programmer to accomplish many tasks. |
Often, there can be several different forms which are bound to the same table. In most cases the forms will share the same foundset and thus provide a unified view. For example, imagine a form showing a list of customer records, where clicking on one of the records switches to another form showing a detailed view of only the selected record. The forms will automatically stay in sync and there is no need to coerce the forms to show the same record. Exceptions to this behavior include scenarios where forms are shown through different Relations, or have been explicitly marked to use a separate foundset.
| Note |
|---|
See also the namedFoundset property of a form. |
| Gliffy Diagram | ||
|---|---|---|
|
...
Overview
Content Tools
Activity