Subject Re: [firebird-support] Re: Read only user
Author Gustavo
Alan also suggested to use a read only transaction but this user will
connect using IB_SQL or something similar. He will not connect using my
application. So how can I use a readonly transaction in this case? Is there
a way to "force" a user to use always a read only transaction?

Gustavo

----- Original Message -----
From: "Alexandre Benson Smith" <iblist@...>
To: <firebird-support@yahoogroups.com>
Sent: Tuesday, October 30, 2007 7:33 PM
Subject: Re: [firebird-support] Re: Read only user


> gstv_m wrote:
>> So, by the moment, the best thing I can do is what Alexandre
>> suggested but I still have the following problems:
>>
>> 1. The user will be allowed to create a table. Is there a way to
>> avoid this?
>>
>
> I really don't know what happens if a user opens a read-only transaction
> and try to create a table... Maybe it works give it a try.
>
>> 2. eMeL said that executing a SELECT with a SP, the read only user
>> can modify the database. Is this true even if I don't grant EXECUTE
>> to this user?
>>
>
> I think he is saying about your SP has code that update the database and
> works as a selectable SP. If you code your SP just to select from a
> table, any user that has no direct access to the table, but have
> privileges to execute that SP, will not change any data.
>
>> Any other suggestion of creating a read only user another way?
>>
>
> nope
>
>> Gustavo
>>
>
> see you !
>
> --
> Alexandre Benson Smith
> Development
> THOR Software e Comercial Ltda
> Santo Andre - Sao Paulo - Brazil
> www.thorsoftware.com.br
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
> __________ InformaciĆ³n de NOD32, revisiĆ³n 2627 (20071030) __________
>
> Este mensaje ha sido analizado con NOD32 antivirus system
> http://www.nod32.com
>
>