I don't know if this can be regarded as a bug, WAD or something else but I'm playing with the inbuilt privileges. I added CREATE to Alf (Fred was busy and then I tried

grant ALL PRIVILEGES on database wobble to alf

and was rewarded with an error

ElevateDB Error #400 The privilege Create already exists.

Whilst this is quite true and factual its not very helpful Is there a reason for telling us rather than just ignoring it and getting on with setting the rest?

Roy Lambert

Roy,

<< I don't know if this can be regarded as a bug, WAD or something else but
I'm playing with the inbuilt privileges. I added CREATE to Alf (Fred was
busy and then I tried

grant ALL PRIVILEGES on database wobble to alf

and was rewarded with an error

ElevateDB Error #400 The privilege Create already exists.

Whilst this is quite true and factual its not very helpful Is there a
reason for telling us rather than just ignoring it and getting on with
setting the rest? >>

Hmmm, I'm of two different minds on this one.  One of the design goals of
EDB is to make sure to inform the developer or user any time an operation
encounters a situation that may be contrary to the expected situation for
such an operation.  However, on the other hand, another design goal is to
ensure that things are as simple and intuitive as possible, so in this case
I think design goal number 2 wins, and I'll just have it ignore such a
situation.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


Ta

Roy Lambert

Hi Tim,

Can you also change this behavior for REVOKE of privileges. If the user
doesn't have the specific right, there would be no need for an error
messages stating that the user does not have this right.

Best regards,
Fons

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:2262DBEB-3A2A-484D-9C0D-22D2189F0E95@news.elevatesoft.com...
> Roy,
>
> << I don't know if this can be regarded as a bug, WAD or something else
> but I'm playing with the inbuilt privileges. I added CREATE to Alf (Fred
> was busy and then I tried
>
> grant ALL PRIVILEGES on database wobble to alf
>
> and was rewarded with an error
>
> ElevateDB Error #400 The privilege Create already exists.
>
> Whilst this is quite true and factual its not very helpful Is there a
> reason for telling us rather than just ignoring it and getting on with
> setting the rest? >>
>
> Hmmm, I'm of two different minds on this one.  One of the design goals of
> EDB is to make sure to inform the developer or user any time an operation
> encounters a situation that may be contrary to the expected situation for
> such an operation.  However, on the other hand, another design goal is to
> ensure that things are as simple and intuitive as possible, so in this
> case I think design goal number 2 wins, and I'll just have it ignore such
> a situation.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Fons,

<< Can you also change this behavior for REVOKE of privileges. If the user
doesn't have the specific right, there would be no need for an error
messages stating that the user does not have this right. >>

Yes, absolutely.  I should have checked the REVOKE behavior when I did the
change for the GRANT.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> Yes, absolutely.  I should have checked the REVOKE behavior when I did the
> change for the GRANT.

Thanks.

Best regards,
Fons