>> There is certainly a weakness in SQL for database definitions to declare
>> more complicated RI.
> is exactly why I don't bother with declarative RI
I still feel that, from a maintenance point of view stronger declarative RI would
be beneficial. I assume as movement towards OODB accelerates we will see
more extensibility in the feedback mechanisms around RI but at present they
are seriously lacking - especially where parsing of error strings is concerned,
hardly the ideal solution especially when dealing with a system that has all the
support code needed to provide the material in it's parsed form. Imagine a system
where a DBServer exception was also accompanied by an Errors Dataset with a
standard classification (and custom sub-classification) column and affected objects
columns - this is certainly a nice way of presenting results back to a client-tier...
Has anyone utilised JADEs OODB... Does it provide any improvements over ORACLE
and MSSQL feedback mechanisms.
--
Aaron Scott-Boddendijk
Jump Productions
(07) 838-3371 Voice
(07) 838-3372 Fax
---------------------------------------------------------------------------
New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
