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
