Date post: | 17-Dec-2015 |
Category: |
Documents |
Upload: | aleesha-rogers |
View: | 226 times |
Download: | 3 times |
System Overview
• Goal– Blend the functionality of a collections management
system with a database management system– Do this through a web application interface
• Why– Existing collections management systems provide poor
support for web pages– Existing database management systems can be overly
complex and intimidating
Design:
Event based design lends naturally to a web interface
Primary object, Table, inherent in a database
Each script represents an action
Design:
•View Data•Create Data•Modify/Delete Data•Create Table•Modify Table•Delete Table•User Management•Settings Management
Event scripts:
Design:Script Execution:
Grab user privilegeGrab user idGrab settings
Verify permissionsPerform action
Header
Scripted Page
Start page layout
FooterFinish page layout
Referential Integrity:
When removing a table can automatically remove for any tables that contain as a foreign key
SQL Bookmarks:
Given the broad scope of Collections Keeper it is inevitable that all cases will be covered.
SQL Bookmarks are there when Collections Keeper can’t do what you want.