I assume there will be some abstraction layer between the application and
the database. We should be able to change from database to database by
changing the abstraction layer rather than changing the application code.
From the application programmer point of view, there will be standard easy
to use commands for saving and loading the project. Perhaps another issue
will be whether the state of the project is continuously stored (i.e. every
time you add a new task, it gets written to disk) or whether the state of
the project is only stored when the Project Manager hits "Save".
Regards,
Shawn
----- Original Message -----
From: "B. Evers" <[EMAIL PROTECTED]>
To: <dev@oopm.openoffice.org>
Sent: Thursday, January 04, 2007 4:13 AM
Subject: Re: [oopm-dev] Base
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <dev@oopm.openoffice.org>
Sent: Thursday, January 04, 2007 2:34 AM
Subject: RE: [oopm-dev] Base
Hi all,
We should consider either defining a strict persistence layer or using a
tool such as Hibernate to isolate the application itself from the actual
data store. By abstracting away the mechanics of data access we can span
a wider array of technologies such as Base, Oracle, PostgreSQL, MySQL,
XML for storage and retrieval.
I totally agree with Gil. By adding this extra layer not only are we
independant of the database to use, but we can also make the application
easy scalable from desktop/single user to enterprise level all using the
same database.
Benno
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.3/614 - Release Date: 1/2/2007
2:58 PM
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
