> Ah, OK. More elegant. But, it still moves responsibility for this
> to the application layer, not the database, itself. I can't see
> any way of avoiding this :-(
Sure, I had a similar problem where newer data is required to specify
certain fields, but a legacy application can't provide that
Don Y wrote:
Hi,
I wasn't prepared to ask this question, yet :< but
all the talk of stored procedures, etc. suggests
this might be a good time to venture forth...
Humor me: assume I have done the analysis and *know*
this to be correct for my situation :>
I want to embed a good deal of the i
On 4/6/06, Don Y <[EMAIL PROTECTED]> wrote:
For example, the title may match an existing entry -- butthe author may be different (e.g., misspelled, or some"other" author listed on a book having multiple authors, etc.).Ideally, I would like the database to suspend the INSERT,
ask for confirmation (a
Bernhard Weisshuhn wrote:
Don Y wrote:
[snip]
For example, the title may match an existing entry -- but
the author may be different (e.g., misspelled, or some
"other" author listed on a book having multiple authors, etc.).
Ideally, I would like the database to suspend the INSERT,
ask for conf
Don Y wrote:
Hi,
I wasn't prepared to ask this question, yet :< but
all the talk of stored procedures, etc. suggests
this might be a good time to venture forth...
Humor me: assume I have done the analysis and *know*
this to be correct for my situation :>
I want to embed a good deal of the i
