Well yes, i find your system very interesting and will maybe use it as
solution for another problem we have ( :-) ), but i fail to see where
it makes use of a primary key referencing another primary key ?
On Fri, Oct 14, 2005 at 08:29:40AM -0700, codeWarrior wrote:
> I dont consider this to be a
I dont consider this to be a design problem... In fact... I do the inherited
table thing pretty routinely... It (table inheritance) works very well if
you need to implement a Sarbanes-Oxley audit trail or a "virtual" rollback
system without the overhead of managing transactions.
Consider the re
- Original Message -
i've got
a strange design question to ask you.It's something I couldn't answer to
while feeling confusely it was anabsolutely BAD thing to do.For
our application, we have developed our own framework which sits ontop of
PostgreSQL. It uses object progr
