Re: [Planner Dev] First patch to database backend -> New version

[Richard Hult <richard imendio com>]

On ons, 2004-07-28 at 23:31 +0200, Alvaro del Castillo wrote:

> We need someplace in database to store the version. I will bet for a
> version for all the data in database, not having a different version for
> each project in database, because it will be too complex.
> 
> What do you think?

Sounds good to me. 

> Ok, I have modified the message to:
> 
> _("Could not create tables in database %s. File %s is not correct."
> 								   "\n\nDatabase error: \n%s"),
> 
> I think it is important to show the filename in order the user could get
> some support from its distribution or from us in the planner user list.

Right.

> > Hm, a question: Couldn't we just go ahead and add create the tables? If
> > the user wants to use the database in the first place, why ask again?
> > 
> 
> I think that it is good that the user knows that something is happening
> first time. If everything is ok, only the first time she will see such
> dialogs. But if something goes wrong, she will receive more information
> and could get more support with the details.
> 
> We can let the code as it is now and see what other people think and
> also, we can test it a bit more to find the best solution.

OK, sounds good.

> 1. We need to create a place in database to store the version for all
> the database data. A single data with one record seems to be a terrific
> waste of resources, but the direct solution. Maybe we can create a
> special property to store it ...
> 
> 2. I need to implement the new dialog with Cancel, Upgrade buttons.

That should just be a matter of changing 1 or 2 lines :)

/Richard

-- 
Imendio HB, http://www.imendio.com/