Subject | Re: [Firebird-Architect] NOT UPDATABLE fields |
---|---|
Author | Adriano dos Santos Fernandes |
Post date | 2005-02-25T11:23:27Z |
Claudio Valderrama C. wrote:
NULL) that will prevent problems in future database maintenance.
Also, applications with generate dialogs based in the metadata can
understand.
Many programs can benefit from it.
For example, value of financial or accounting movement can't be changed.
Adriano
>Adriano dos Santos Fernandes wrote:I want something that work for all users and is easy to do (like NOT
>
>
>>>Adriano,
>>>
>>>Do you meant that the value should be only provided on insert, and
>>>no update be allowed ?
>>>
>>>
>>>
>>>
>>Yes and the value should be updatable in "on insert triggers".
>>But not with UPDATE statement and in "on update triggers".
>>
>>
>
>Currently, we only support a specific list of fields in grants statements
>associated with UPDATE and REFERENCES. Isn't this what you are looking for?
>
>create role cat;
>grant update(a) on t to role cat;
>
>Fields not specified can't be updated by users that attached to the db with
>role cat.
>
>
NULL) that will prevent problems in future database maintenance.
Also, applications with generate dialogs based in the metadata can
understand.
Many programs can benefit from it.
For example, value of financial or accounting movement can't be changed.
Adriano