|
|
 |
|
|
|
Schema Evolution
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Templates
Windows
Folders
Web, E-mail and File Links
User Interface
Schema Evolution
|
|
|
|
Since FastOrganizer is so flexible one thing that it must contend
with is schema evolution. Schema evolution is a term commonly
applied to relational databases when rows in a table must be updated
for changes in the table layout. In the case of FastOrganizer
a similar issue can occur. When a templete is changed and one
or more windows use that template for layout, FastOrganizer must
perform schema evolution. From the very beginning
FastOrganizer has been designed to be flexible. At any time a
user can change the layout of a template and all the windows that
depend on that template will be updated automatically.
For this reason, FastOrganizer has been designed to handle all
aspects of schema evolution. This ensures that users can
change their data layout at any time with the confidence the
FastOrganizer will keep everything in synch. A user cannot
break FastOrganizer.
|
|
|
|
Now available for immediate purchase
FastOrganizer 2.13.2
Moto_Template.fast
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Now available for immediate download FastOrganizer
Evaluation Version
(Limited to 45 total items)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|