Subject | Re: [IBO] How to set readonly flag from grant on dataset fields |
---|---|
Author | henry FRANQUET |
Post date | 2004-08-04T13:19:24Z |
--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
I only mean that on a TIBODataset when I don't define any field,
fields are automatically defined on opening, but when I define
fields they become permanent and on opening no extra field
definition occurs. My need is using permanent fields for lookup and
calculated fields and automatically add all the other fields of the
table (as database definition may vary)
Then I'll use rdb$user_privileges to get user's rights. End-user
have to know their right about a field as soon as it is displayed
datatype of fields, domain name, default values, check values,
indexes, foreign keys and so on
> At 02:51 PM 2/08/2004 +0000, you wrote:thanks for your reply
> >Hi
> >
> >I use TIBOTable in Delphi 5 with Firebird 1.5, sometimes with
> >automatic fields definition and most of the time with permanent
> >fields (best of all would have been : automatic fields definition
> >with some permanent one !).
>
> I have no idea what you mean by this! :-)
I only mean that on a TIBODataset when I don't define any field,
fields are automatically defined on opening, but when I define
fields they become permanent and on opening no extra field
definition occurs. My need is using permanent fields for lookup and
calculated fields and automatically add all the other fields of the
table (as database definition may vary)
> -- snip --does native IBO take care of privilege ?
> >As I would allow end user DBA to set granting on columns, I wonder
> >how to have automatic setting on field definition depending of
> >grants (first of all read-only flag set)
>
> and/or (because you are not using native IBO)
> -- snip --were set
> You would need to have very exact knowledge of how the privileges
> since it is between "hard" and "impossible" toEnd user DBA use a application feature to set privileges.
> manage SQL privileges without a properly-designed scheme.
Then I'll use rdb$user_privileges to get user's rights. End-user
have to know their right about a field as soon as it is displayed
> -- snip --at startup
> The logic would be quite horrendous and the application overhead
> would be significant.I already read the entire database scheme at start up to have exact
datatype of fields, domain name, default values, check values,
indexes, foreign keys and so on