Thanks Andre for your views. I think I am getting an idea on how I might
go about your suggestion to RL_Writers, which I can create on the
development database copy. This role then can be taken to the production
database via the utility that manages other DML operations.

The users that are already there or a newly created then can rely on
this RL_Writers without me worrying on the production copy of who the
end users might be. Please correct me if I have not followed your
suggestion.

Let me see how this goes.

Kind regards
Bhavbhuti

On 03/12/2012 07:06 pm, André Knappstein wrote:
>
> It's not possible the way you describe it. You can't have any group
> of users, which are not SYSDBA, automatically privileged for DML as
> soon as a relation is created or its metadata was changed.
>
> You need to explicitely "grant" the privileges.
>
> For this purpose though, you can easily set up *one* role, for example
> "RL_Writers". You still need to create all users, and assign them to
> that role. Whenever you create a new relation, all you need is one
> more command "grant all on <relationname> to RL_Writers".
>
> have fun!
> André
>
> > Hi all
>
> > Presently I do not create users in FireBird and rely on the sysdba
> > login to auto update data structures and user data-entry from the
> > application. I know this is not good but had to get things forward.
>
> > I need a couple of types of users in FireBird. One, are the
> > data-entry users. They should be able to add, edit, delete and
> > query records via the application. What kind of a FireBird user is
> > this? They need to get access to all the tables and fields
> > automatically as and when created/updated for data purposes.
>
> > Another, is the sysdba. This user is required when the app is
> > updated and the DML are executed via the utility to update
> > structures. Also required for connecting to the database for
> > updating the Remote Views to work on the data in FireBird in the
> > application. Password to this sysdba is a concern too, I am fine to
> > just change it and not create a full admin on the production
> > database but am open to suggestions but am looking towards a lot of
> > automation using DML via a utility just for this purpose.
>
> > Ideas and advise please.
>
> > Thanks and regards
> > Bhavbhuti
>
>

--


Thanking you.

Yours Faithfully,
For Venus Software Operations
----
Mr. Bhavbhuti Nathwani
___________________________________________
Softwares for Indian Businesses at: http://www.venussoftop.com

venussoftop@...
venussoftop@...
___________________________________________

Please note: We reserve complete rights for policy changes in the future and the same will be applicable immediately as and when made. Attachments may get corrupted before reaching you, in such a situation please let us know and we will resend you the same at the earliest. We do not take any responsibility for data loss of any type and kind. Data safety remains the sole the responsibility of the users of our softwares.
___________________________________________

Internet email confidentiality:

This message may contain information that may be privileged or confidential. If you are not the addressee nor are you responsible for the delivery of the message to the addressee indicated in this email, then you may not copy or deliver this email to anyone and you should notify the sender by reply email and then destroy this message.

Please reply email immediately to this message with REMOVE in the subject, if you or your employer do not consent to email of this kind.

Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by my company.