Martijn Tonies wrote:

>>>Should NOT UPDATABLE be considered as form of _constraint_
>>>or as a form of _privilege_ ? If the later, does it restrict sysdba too
>>>
>>>
>?
>
>
>>Constraint, restricting database owner and sysdba too.
>>
>>
>
>Hmm... I wonder what happens if you accidentally inserted
>the wrong value :-)
>
>With regards,
>
>Martijn Tonies
>Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
>Server
>Upscene Productions
>http://www.upscene.com
>
>

Martijn,

Sorry if I missed the joke :-)

I think Adriano is talking about account records that can't be changed,
if someone inserts the wrong values he should cancel that movement with
a reverse operation (like debit and credit in the banck account).

Even if it can be done on triggers, as said before, I prefer declarative
constraints.

I think Ann has resumed very well the proposal. Even if this declarative
constraint generate automatically the trigger code (like with other
constraints), I think this will easy the database designer life and make
the schema and the designer goal more clear, readable and intuitive.

see you !

--

Alexandre Benson Smith
Development
THOR Software e Comercial Ltda.
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br



--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 22/02/2005