Hello, All.
Is subj possible?
If I write in database.conf something like this:
MyDB=MyDB
{
Foo=Bar
}
Which interface a plugin can use to get Bar for Foo when it is loaded
for this
database?
--
WBR, SD.
On 07/03/14 12:34, Dimitry Sibiryakov wrote:
03.07.2014 10:23, Alex Peshkoff wrote:
Which interface a plugin can use to get Bar for Foo when it is
loaded for this
database?
IFirebirdConf.
I tried, but getKey(Foo) returns -1.
What did I wrong?
In databases.conf one can use
03.07.2014 12:45, Alex Peshkoff wrote:
In databases.conf one can use only present in firebird.conf fixed set of
parameters.
See config.cpp for details.
I suppose we have no problems adding replication parameters in it.
I don't think *plugin-specific* settings belong to our config.
Dmitry
03.07.2014 11:04, Dmitry Yemanov wrote:
I don't think*plugin-specific* settings belong to our config.
Ok. Is there a place where user can put database-wide parameters and where a
plugin can
get it from exactly for the database it was loaded for?
--
WBR, SD.
03.07.2014 11:14, Alex Peshkoff wrote:
Ok. Is there a place where user can put database-wide parameters
and where a plugin can
get it from exactly for the database it was loaded for?
No. Do you have a suggestion?
IMHO, databases.conf is an obvious (from end-user POV) and the best
03.07.2014 13:18, Dimitry Sibiryakov wrote:
No. Do you have a suggestion?
IMHO, databases.conf is an obvious (from end-user POV) and the best place.
Or just pass the database name into plugin and allow it to store/parse
its own config (database-wide or global) in whatever way the developer
On 07/03/14 13:26, Dmitry Yemanov wrote:
03.07.2014 13:18, Dimitry Sibiryakov wrote:
No. Do you have a suggestion?
IMHO, databases.conf is an obvious (from end-user POV) and the best place.
Or just pass the database name into plugin and allow it to store/parse
its own config (database-wide
03.07.2014 11:27, Alex Peshkoff wrote:
Mixing plugin-specific parameters with firebird parameters in same heap
is bad idea. Mixing 2 sets of parameters of 2 plugins in same heap is
even more bad - each plugin would like to have parameter 'Foo' for
different purporses. Can we suggest a format
03.07.2014 13:25, Alex Peshkoff wrote:
This syntax fits much better into current config files.
Can GetPlugins() handle it?
--
WBR, SD.
--
Open source business process management suite built on Java and Eclipse
On 07/03/14 15:36, Dimitry Sibiryakov wrote:
03.07.2014 13:25, Alex Peshkoff wrote:
This syntax fits much better into current config files.
Can GetPlugins() handle it?
How is it related with GetPlugins?
--
Open
03.07.2014 13:58, Alex Peshkoff wrote:
On 07/03/14 15:36, Dimitry Sibiryakov wrote:
03.07.2014 13:25, Alex Peshkoff wrote:
This syntax fits much better into current config files.
Can GetPlugins() handle it?
How is it related with GetPlugins?
GetPlugins() will have to work with such
On 07/03/14 16:04, Dimitry Sibiryakov wrote:
03.07.2014 13:58, Alex Peshkoff wrote:
On 07/03/14 15:36, Dimitry Sibiryakov wrote:
03.07.2014 13:25, Alex Peshkoff wrote:
This syntax fits much better into current config files.
Can GetPlugins() handle it?
How is it related with GetPlugins?
03.07.2014 14:09, Alex Peshkoff wrote:
Parameter of plugin is something different from the list of plugins of
given type, used by GetPlugins.
From your syntax I decided that you suggest to combine them.
--
WBR, SD.
13 matches
Mail list logo
