Subject | RE: [IBO] Users: always connect ISC4.GDB? |
---|---|
Author | Christian Gütter |
Post date | 2001-01-23T09:32:10Z |
Claudio,
at least one answer :-(
sceonds.
procs and the thought of putting a UDF into my database makes me shiver.
The ISC4.GDB is really a downside of IB - I won't blame you ;-)
I am thinking of synchronizing the USERS table of ISC4 with a table in my
production database each time one client app starts.
So I would have a selectable list of users which can quickly be accessed.
Due to the fact that new users are not added very often and only SYSDBA is
able to change their passwords, it shouldn't be risky to proceed in this
way.
What do you think?
With regards,
Christian
at least one answer :-(
> If you want the list of users without touching directlyThis could be OK - better than always connecting ISC4 and wasting two
> isc4.gdb (what an
> horrible name, BTW), you should make a call to the Services API.
sceonds.
> (You could write an UDF for such purpose and call itThis is exactly what I don't want to do - I like the idea of stored
> from your procedure if
> you want to do all things inside the server and not from the
> client app, but
> if you run into problems, don't blame me, please.)
procs and the thought of putting a UDF into my database makes me shiver.
The ISC4.GDB is really a downside of IB - I won't blame you ;-)
I am thinking of synchronizing the USERS table of ISC4 with a table in my
production database each time one client app starts.
So I would have a selectable list of users which can quickly be accessed.
Due to the fact that new users are not added very often and only SYSDBA is
able to change their passwords, it shouldn't be risky to proceed in this
way.
What do you think?
With regards,
Christian