>> No, that's not what it is -- Database Workbench will connect to the >> database, >> via the server, providing a username/password combination. >> >> But after that, it can provide the user with a list of available user >> names >> for >> the use in the Grant Manager. >> >> Firebird 3 always provides a SEC$USERS table, either from the server wide >> user database OR from the secondary user database. >> >> But for user management, I would like to know if the users list comes >> from >> the >> server or from a secondary database, it would be more clear to the users >> of Database Workbench to see the difference if there's NO "Users" node >> for a database which users server side users, and there is a "Users" node >> for databases that use a secondary user database. > >Well understood at least (I hope). >This requires small fix in code processing isc_info_svc_user_dbpath >(make it depend upon isc_spb_expected_db). This will help you know what
The only thing I would need is a simple flag saying - more or less - "this is using a secondary database". >security database is used by given database using services. Please add a >ticket to the tracker - such small enhancement may be added in beta2. I >understand that using mon$ tables could be better but afraid for FB3 >time for such changes is gone. I would certainly prefer an SQL based solution, as API changes can be tricky some times and I mostly avoid them, as I, and many others, are relying on a third party for support for new calls/features/tweaks/constants. With regards, Martijn Tonies Upscene Productions http://www.upscene.com Download Database Workbench for Oracle, MS SQL Server, Sybase SQL Anywhere, MySQL, InterBase, NexusDB and Firebird! ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
