[GENERAL] Multi-table CHECK constraint

I need to add some complex constraints at the DB. For example. Do not allow a line item of inventory to be changed if it does result in the same number of joints originaly shipped. These will involve several tables. What is the best approach for this? Here is what I have been trying.

[GENERAL] Multi-table CHECK constraint

I need to add some complex constraints at the DB. For example. Do not allow a line item of inventory to be changed if it does not result in the same number of joints originally shipped. These will involve several tables. What is the best approach for this? Here is what I have been trying.

Re: [GENERAL] Multi-table CHECK constraint

On Wed, Dec 10, 2008 at 3:58 PM, Jason Long [EMAIL PROTECTED] wrote: I need to add some complex constraints at the DB. These will involve several tables. What is the best approach for this? Well ANSI-SQL provides the CREATE ASSERTION for this purpose. However, PostgreSQL doesn't support this

Re: [GENERAL] Multi-table CHECK constraint

Richard Broersma wrote: On Wed, Dec 10, 2008 at 3:58 PM, Jason Long [EMAIL PROTECTED] wrote: I need to add some complex constraints at the DB. These will involve several tables. What is the best approach for this? Well ANSI-SQL provides the CREATE ASSERTION for this purpose. However,

Re: [GENERAL] Multi-table CHECK constraint

On Wed, Dec 10, 2008 at 05:58:08PM -0600, Jason Long wrote: I need to add some complex constraints at the DB. For example. Do not allow a line item of inventory to be changed if it does not result in the same number of joints originally shipped. These will involve several tables. What

Re: [GENERAL] Multi-table CHECK constraint

On Wed, Dec 10, 2008 at 05:58:08PM -0600, Jason Long wrote: I need to add some complex constraints at the DB. For example. Do not allow a line item of inventory to be changed if it does not result in the same number of joints originally shipped. These will involve several tables.