Hi!
The database create/upgrade patch only misses actually a way to know the
version for planner database. Thinking about how we can save in database
the version (needed for the upgrade system), I finally think that the
best thing we can do is to store it in "property" table as a "text"
property.
property records are related to projects in table "project_to_property"
so it could be clear that if a property isn't in project_to_property, it
is a global property for all planner projects, like the database
version.
But we can't do it that way because properties types are related to
projects. So if we want to use a property to store the database version,
we need a pseudo-project in which to store the global properties for
planner. I am not sure how "hackish" it sounds to you. For me yes, it is
a bit hackish but the other solution will be to create a separate table:
CREATE TABLE property_global (
prop_id serial,
prop_name text NOT NULL,
value text,
PRIMARY KEY (prop_id)
);
Then we can't have different properties types as in properties for
projects but you know, in this table for the moment we will have only 1
record and I can't think now about other things we ca store here.
I think I will follow the new table approach but, what do you think?
http://cvs.gnome.org/viewcvs/planner/data/sql/database-0.11.sql?rev=1.1&view=auto (database tables)
Cheers
-- Alvaro
Attachment:
signature.asc
Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente