Re: DB?

Mikael Hallendal wrote:

>
> Yes, a database backend is planned (probably by using libgda which gives
> transparent support for different backends, mysql, postgreSQL and
> possibly others).
>
> What I'm unsure of is that when you work in this mode. Do you want your
> changes to be written back directly (you change something in the UI and
> it's updated on the database directly). Or do you want something like
> "save" or "update database" instead.
>
> If you want the first, it's harder to implement, if you want the second
> it's a piece of cake.
>

Hi  - its me the p3 user again - P3 actually does both after a fashon - changes
not involving dates are written immediatly, dates and related numbers are
calculated at the update (applied current data date) - sometimes this causes a
situation where a resource must be deleted and added new because the forecast
calculations must be innitialized. Since the dates are in the database it is easy
to do monthly or quarterly summaries or even sliding reports showing the
calculated dates from a series of updates (because the database file is usually
renamed at each update and retained) These features also allow the creation of
various targets and scenerios which can also be reported and displayed graphicly
in various ways.  If you go too far down this path you may have to change your
thinking about resources and calanders, maybe a different software is needed for
large projects.  P3 is expensive software. and must be paid year by year because
the complexity cannot be learned out of a book - I have used it since the
original IBM PC first came out and learned stuff bit by bit. New users are forced
to attend expensive training and spend hours on the phone with tech support just
to keep going from month to month. Hmm this begins to sound like a business model
for open source. #;->