On 20 Oct 2005 at 14:53, A-NO-NE Music wrote: > David W. Fenton / 2005/10/20 / 02:40 PM wrote: > > >Finale files are database files > > It is?! > What is the definition of the database file? > > I don't consider it is a database if you don't push/pop and real-time > data I/O. If real-time data I/O then I will agree it is a corruption, > but Finale file is not, to my eyes.
Finale is not a database program, but Finale's data is stored in a database structure. There is a database program sitting in between Finale's UI and the data file that delivers data to Finale and writes the edits recieved from the Finale UI into the data structure. Think of it this way: When you go to Amazon.com, you are not running a database -- you're running an application in a web browser. But when you do a search, the Amazon search application is using a database to retrieve the data for you. Likewise, if you place an order on Amazon.com, the order form can be edited in your browser, but nothing happens to the database until you submit your changes, which are passed off to Amazon's ordering application, which takes care of writing data to the database(s) involved. With Finale, there's no SUBMIT operation required. Your changes are posted to the in-memory copy of the database as soon as you make them. And that's separate from the disk image of the database, which is updated only when you do a manual save. It's analogous (though not the same) as the use of commit/rollback transactions in a database (indeed, Finale's UNDO may very well be implemented at the database level with a commit/rollback model specific to the database engine involved). Until you save the file, the changes you've made in memory are not committed to the stored disk image of the file. -- David W. Fenton http://www.bway.net/~dfenton David Fenton Associates http://www.bway.net/~dfassoc _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
