... and remember to get the user to define the insert/update/delete
priorities:
should a delete/insert pair be treated as an update?
or should an insert/delete pair be treated as no-op?
an insert/update pair should normally be allowed, but will delete/update
(or any non-existing record) throw an error?
Will the whole job be aborted on errors?
These sort of questions go way back to batch-processing and tape drives!
- which makes me wonder just why anyone would ever want to do this on an
RDB?
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
