<mbrown@fensystems.co.uk> Create a query that looks something like: SELECT pupils.name, fsm_status(pupils.id, today), fsm_status(pupils.id, today+1), ...
<mbrown@fensystems.co.uk> Procedure creation and trigger creation is separate - you create
procedure first and then you can create a trigger that calls it if you want. You don't have to use triggers - they just seem to me to be the most obvious way to hook the procedures in, because you can
Still thinking about that. Without actually posting table definition statements here, its hard to figure out whether this solution would be possible. Do you know of any (cross-platform and free, not asking a lot!) tools for producing ER diagrams so the discussion could get more definite? I have never used any such tool, other than whats built into Access, because I have never had to discuss overall database structure with anyone other than myself. <rjg@ateb.co.uk> earlier mentioned the DfEE 'Common Basic Data Set' , any design should be mindful of this, but interest in a successful design with running examples might extend beyond the UK. the then make
almost everything invisible to the database client, giving you a 'clean' interface to the DB.
Can you call the procedures other than via a trigger? Also, what language would you write procedures in? Looking at the postgresql pages, which I referenced earlier, it seems quite a low level task, where you connect it so some other language of your choice, C being given there as an example. My C programming does not extend a great deal further than Hello World. The time it would take to be productive on a given system is important. I have to say that I have never written a line of Interbase procedure code either. Are there visual tools for interacting with a postgresql backend, again x platform? Interbase has several. Richard richard@tortoise.demon.co.uk