Re: Triggers - :new - pseudorecord

From: Jeremy <jeremy0505_at_gmail.com>
Date: Tue, 17 Sep 2013 06:36:20 +0100
Message-ID: <MPG.2ca1faa6fb6e5af298973b_at_news.individual.net>


In article <0ee09b41-bc62-431e-b00b-36f44d640d65_at_googlegroups.com>, joel-garry_at_home.com says...
> Having dealt with "database blind" and "infinitely flexible schema" stuff in databases for far too long, I would run screaming from what you are trying to do, as minimizing the maintainability effort in that manner maximizes the maintainability effort in a more fundamental manner. But that probably just reflects the horribly bad way I've seen xml abused, as well as keeping referential integrity in the app and other such religious persecution.
>
> But don't let me stop you.
>

No you misunderstnd me - the *original* idea was around XML which already attracted sufficient negative feedback that we have elsected to implement shadow tables which more or less mirror the tables we are tracking change on. Downside is that it appears that the developers have code some column assignments :)

-- 
jeremy
Received on Tue Sep 17 2013 - 07:36:20 CEST

Original text of this message