Re: [Planner Dev] Database schemas, versions and upgrading paths

[Richard Hult <richard imendio com>]

On tor, 2004-07-01 at 09:57 +0100, lincoln phipps openmutual net wrote:
> 
> Alvaro del Castillo wrote:
> 
> > Hi guys!
> > 
> > I am working in coding the database schema from a file. We will do it
> > when the SQL module storage is loaded and I imagine the steps like:
> > 
> > 1. Check if we have any planner SQL schemas:
> > 
> > 	1.1 If we don't have any schemas we try to load the schemas from 	the
> > file database-VERSION.sql. If we can't find the file, we 	have to report
> > an error to the user. If we find the file, we'll 	load it in the
> > database and continue execution. 
> > 
> > 	1.2 If we have them, then go 2.
> > 
> > 
> > 2. If 1.2 then check if we have the correct tables in the database:
> 
> 
> To do this we really need that "planner" table which I was thinking
> about which contains....
> 
> 	tables_dtd  (text field)
> 
> as well as the other things (tables_prefix etc). This would
> contain the "0.11" text. Though we know what we mean I want to
> avoid the word "schema" as its a postgres database term.

Why not "version"? DTD is specific to the xml backend.

/Richard

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