> 28.10.2014 19:06, Martijn Tonies wrote:
>
> > MON$SEC_DATABASE_USED
> > values: "DEFAULT" / "SECONDARY"
>
> Maybe "DEFAULT", "SELF", "OTHER"?
>
> I may imagine cases when EUA and "other-non-default" dbs should be
> distinguished.
Rather than "MON$SEC_DATABASE_USED" name, "MON$SEC_DATABASE"
>> (which reminds me: I had no idea how to create a secondary user database
>> which is why I copied the server wide one into another location)
>
>To make any database a security one you should make appropriate changes
>in databases.conf, connect to it in embedded mode as sysdba and execute
>CREATE
>28.10.2014 17:19, Martijn Tonies (Upscene Productions) wrote:
>> And "other non default" would be a few databases using a single secondary
>> security database?
>
> There is no such thing as a "secondary security database".
Potato potato...
---
On 10/28/14 19:53, Dimitry Sibiryakov wrote:
> 28.10.2014 17:48, Alex Peshkoff wrote:
>> Should be:
>> security.db = $(dir_secDb)/security3.fdb
> I wonder why it isn't "security3.fdb = $(dir_secDb)/security3.fdb".
To be able later in any version have embedded connections to it as
"security.db
28.10.2014 17:48, Alex Peshkoff wrote:
> Should be:
> security.db = $(dir_secDb)/security3.fdb
I wonder why it isn't "security3.fdb = $(dir_secDb)/security3.fdb".
At first I though that you changed hardcoded security DB name and this is
the way to be
backward compatible...
--
WBR, SD.
On 10/28/14 19:37, Dimitry Sibiryakov wrote:
> 28.10.2014 17:34, Alex Peshkoff wrote:
>>> BTW, what declaration of "security.fdb" in default databases.conf is
>>> for?
>> To make it use small cache (saves memory when default one is big) and
>> avoid remote connections to it.
> Why it is
28.10.2014 19:37, Dimitry Sibiryakov wrote:
> Why it is "security.fdb", not "security3.fdb" then?..
Actually, it's "security.db", not "security.fdb" ;-)
security.db = $(dir_secDb)/security3.fdb
Dmitry
--
Firebird-Dev
28.10.2014 17:34, Alex Peshkoff wrote:
>> BTW, what declaration of "security.fdb" in default databases.conf is
>> for?
>> >
> To make it use small cache (saves memory when default one is big) and
> avoid remote connections to it.
Why it is "security.fdb", not "security3.fdb" then?..
--
On 10/28/14 19:31, Dimitry Sibiryakov wrote:
> 28.10.2014 17:27, Dmitry Yemanov wrote:
>> Other = everything neither self nor security3.fdb.
> BTW, what declaration of "security.fdb" in default databases.conf is for?
>
To make it use small cache (saves memory when default one is big) and
avoi
On 10/28/14 19:19, Martijn Tonies (Upscene Productions) wrote:
> Hello Dmitry,
>
>>> MON$SEC_DATABASE_USED
>>> values: "DEFAULT" / "SECONDARY"
>> Maybe "DEFAULT", "SELF", "OTHER"?
>>
>> I may imagine cases when EUA and "other-non-default" dbs should be
>> distinguished.
> What would "self" mean? Ar
28.10.2014 17:27, Dmitry Yemanov wrote:
> Other = everything neither self nor security3.fdb.
BTW, what declaration of "security.fdb" in default databases.conf is for?
--
WBR, SD.
--
Firebird-Devel mailing list, we
28.10.2014 19:19, Martijn Tonies wrote:
>
> What would "self" mean? Are the security tables inside the database
> you're connecting to?
Self = EUA. Not just having security tables but actually known to be
authenticated using them while connecting.
> And "other non default" would be a few databas
28.10.2014 17:19, Martijn Tonies (Upscene Productions) wrote:
> And "other non default" would be a few databases using a single secondary
> security database?
There is no such thing as a "secondary security database".
--
WBR, SD.
---
Hello Dmitry,
>> MON$SEC_DATABASE_USED
>> values: "DEFAULT" / "SECONDARY"
>
>Maybe "DEFAULT", "SELF", "OTHER"?
>
>I may imagine cases when EUA and "other-non-default" dbs should be
>distinguished.
What would "self" mean? Are the security tables inside the database
you're connecting to?
(which r
28.10.2014 19:06, Martijn Tonies wrote:
> MON$SEC_DATABASE_USED
> values: "DEFAULT" / "SECONDARY"
Maybe "DEFAULT", "SELF", "OTHER"?
I may imagine cases when EUA and "other-non-default" dbs should be
distinguished.
Dmitry
--
On 10/28/14 19:01, Dmitry Yemanov wrote:
> 28.10.2014 18:55, Alex Peshkoff wrote:
>
>> What if I also add that info not to SEC$USERS but to MON$DATABASE?
> No problem, but what is that "info"? Name of the security db or what?
>
> I'm asking because we had plans to introduce all config settings (act
>> What if I also add that info not to SEC$USERS but to MON$DATABASE?
>
>No problem, but what is that "info"? Name of the security db or what?
Hurray!
A column saying anything along the lines of "this is a secondary user
database" is fine.
MON$SEC_DATABASE_USED
values: "DEFAULT" / "SECONDARY"
?
28.10.2014 18:55, Alex Peshkoff wrote:
> What if I also add that info not to SEC$USERS but to MON$DATABASE?
No problem, but what is that "info"? Name of the security db or what?
I'm asking because we had plans to introduce all config settings (actual
to this database) via a new MON$ table. So S
>> I understand that using mon$ tables could be better but afraid for FB3
>> time for such changes is gone.
>
>Feel free to modify SEC$USERS, if needed. I'm likely to commit changes
>for MON$ tables before Beta 2 as well.
I think MON$DATABASE would make more sense.
With regards,
Martijn Tonies
On 10/28/14 18:50, Dmitry Yemanov wrote:
> 28.10.2014 18:28, Alex Peshkoff wrote:
>
>> I understand that using mon$ tables could be better but afraid for FB3
>> time for such changes is gone.
> Feel free to modify SEC$USERS, if needed. I'm likely to commit changes
> for MON$ tables before Beta 2 as
28.10.2014 18:28, Alex Peshkoff wrote:
> I understand that using mon$ tables could be better but afraid for FB3
> time for such changes is gone.
Feel free to modify SEC$USERS, if needed. I'm likely to commit changes
for MON$ tables before Beta 2 as well.
Dmitry
--
28.10.2014 16:28, Alex Peshkoff wrote:
> This requires small fix in code processing isc_info_svc_user_dbpath
> (make it depend upon isc_spb_expected_db).
Will it break possibility to get security database patch without connecting
to a
database? I mean that existing applications that manage us
>> 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 pr
On 10/28/14 18:00, Martijn Tonies (Upscene Productions) wrote:
>> It's only .exe, that's why I've never used to work with it.
> Wine is your friend. ;)
I have and use it but I very often need to check fbclient too, therefore
for firebird it's not an option for me. On the other hand I do not need
If possible, I would like to enable a “User Editor” once connect to the
database inside Database Workbench
>>> I suppose it's a kind of client tool, but how can solution be oriented
>>> for specific one?
>> Here's Database Workbench:
>> http://www.upscene.com/database_workbench/
>>
>> Thi
25 matches
Mail list logo
