2.18 Goals

MattyT matty at chariot.net.au
Sat Sep 14 08:37:12 UTC 2002

On Sat, 2002-09-14 at 14:07, Bradley Baetz wrote:

> If you just mean a way of representing the transitions rather than
> requring the db to ensure that it holds, sure, there are proobably several
> ways of doing it.

How did we get onto transitions?  I was referring to storing query URLs
as a set of records pointing to the relevant ID.

> In practice, though, I still haven't been convinced that _totally generic
> customised status transitions/etc are likely to be used by anyone. A
> smaller subset (say, adding an extra state between two others) is probably
> going to be more useful. There wil still be hard coded statues, such as
> UNCONFIRMED, NEW, etc, or, rather, hard coded ids (the names could be
> changable, in theory)

I have no intention of having "hardcoded" statuses when I customise
them.  Things such as confirmation, resolution, etc can be represented
cleanly by predicates on status records.
         Matthew Tuck: Software Developer & All-Round Nice Guy        
 My Short Autobiography: 1985 Grade Bin Monitor 1990 Class Clown Award
1992 Awarded Most Likely To Spontaneously Combust 1996 Crowned Galactic
         Emperor 1998 Released From Smith Psychiatric Hospital

More information about the developers mailing list