Re: cost of empty fields

On Thu, Apr 21, 2005 at 04:19:02AM +0200, Enrico Weigelt wrote:
> * Jim C. Nasby <decibel(at)decibel(dot)org> wrote:
> > If you setup rules on the view and just have the application select,
> > insert, update, and delete from the view instead of the raw tables you
> > won't need to change your application at all. Though you do need to be
> > aware that you can't easily enforce uniqueness across multiple tables.
> hmm. that doesnt sound stable enough for me.
> this table is really critical and there's a lot of money in game
> (realtime currency trading ...)

Note I didn't say you couldn't do it, I just said it wasn't easy. Easy
as in adding a normal unique constraint. In this case, you need to add
triggers to the tables to check for uniqueness. It's absolutely stable,
it's just not as nice as it could be.
--
Jim C. Nasby, Database Consultant decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"