On Fri, Nov 13, 2015, at 22:47, firebi...@yandex.ru wrote:
> I believe it was replication.conf 😉 It has a section that
> confused you. It was presented using a v2.5 build so it uses the v2.5
> trace config syntax. Of course it will be different in later FB versions.
That's probably right. :)
Wha
> -Original Message-
> From: Alex Peshkoff [mailto:peshk...@mail.ru]
> Sent: Viernes, 13 de Noviembre de 2015 7:25
>
> On 11/13/2015 01:17 PM, Vlad Khorsun wrote:
> >
> > interface LoadedModuleInfo : Versioned
> > {
> > const string getModuleName();
> > ...
> > }
>
> It should be Ref
> Interesting. I was really sure it was databases.conf.
I believe it was replication.conf 😉 It has a section that confused
you. It was presented using a v2.5 build so it uses the v2.5 trace config
syntax. Of course it will be different in later FB versions.
Dmitry
On Fri, Nov 13, 2015, at 17:51, Alex Peshkoff wrote:
> It's from trace config for FB 2.5. It's really XML-like. In FB3 all
> config files follow { } style.
Interesting. I was really sure it was databases.conf. Never mind. Thanks
for clarifying that up.
--
Mgr. Jiří Činčura
Independent IT Special
13.11.2015 12:43, Alex Peshkoff wrote:
> Performing long jobs in module startup entry point is not good from at
> least one POV - plugin manager mutex is locked at this moment and all
> other plugins related activity is impossible.
So, it would be enough not to use plugin manager with mutex, no
13.11.2015 11:25, Alex Peshkoff wrote:
> So we have an agreement with adding Status to FB_PLUGIN_ENTRY_POINT, but
> leaving Master as second parameter?
Have you noticed, that plugin entry point become more and more like
IFactory::createPlugin()?..
--
WBR, SD.
12.11.2015 23:24, Vlad Khorsun wrote:
> 13.11.2015 0:02, Dimitry Sibiryakov wrote:
>> >12.11.2015 22:30, Vlad Khorsun wrote:
>>> Yep. As I said, good old style plugins: separate library for
>>> each, a definite entry
> point for each type which returns ready-to-use plugin c
On 11/13/2015 10:58 AM, Jiří Činčura wrote:
> Hi *,
>
> May I kindly ask why the firebird.conf/databases.conf uses XML-like format
> (although it's not XML) but plugins.conf uses different one using curly
> braces etc.?
>
Firebird following the Linux/Unix convention that all product
configurati
On 11/13/2015 07:33 PM, Jiří Činčura wrote:
> I saw `` with some per database settings in
> today's presentation on Firebird seminar in Prague. Not sure whether it
> was Dmitry or Alexey. Kind of surprised me. :o
>
It's from trace config for FB 2.5. It's really XML-like. In FB3 all
config files f
I saw `` with some per database settings in
today's presentation on Firebird seminar in Prague. Not sure whether it
was Dmitry or Alexey. Kind of surprised me. :o
--
Mgr. Jiří Činčura
Independent IT Specialist
On Fri, Nov 13, 2015, at 17:06, Alex Peshkoff wrote:
> On 11/13/2015 06:58 PM, Jiří Či
On 11/13/2015 06:58 PM, Jiří Činčura wrote:
> Hi *,
>
> May I kindly ask why the firebird.conf/databases.conf uses XML-like format
XML ???
Where did you find it ?
> (although it's not XML) but plugins.conf uses different one using curly
> braces etc.?
>
Hi *,
May I kindly ask why the firebird.conf/databases.conf uses XML-like format
(although it's not XML) but plugins.conf uses different one using curly braces
etc.?
--
Mgr. Jiří Činčura
Independent IT Specialist
--
Fi
On 11/13/2015 01:37 PM, Adriano dos Santos Fernandes wrote:
> On 13/11/2015 08:25, Alex Peshkoff wrote:
>> On 11/13/2015 01:17 PM, Vlad Khorsun wrote:
>>> 13.11.2015 11:21, Alex Peshkoff wrote:
>>>
> So the prototype will become:
>
> void FB_PLUGIN_ENTRY_POINT(IStatus*, IPluginInitializ
On 13/11/2015 08:25, Alex Peshkoff wrote:
> On 11/13/2015 01:17 PM, Vlad Khorsun wrote:
>> 13.11.2015 11:21, Alex Peshkoff wrote:
>>
So the prototype will become:
void FB_PLUGIN_ENTRY_POINT(IStatus*, IPluginInitialization*);
>>> OK, let's pass here more generic interface. Though curr
13.11.2015 12:25, Alex Peshkoff wrote:
...
> So we have an agreement with adding Status to FB_PLUGIN_ENTRY_POINT, but
> leaving Master as second parameter?
Yes, as for me.
Regards,
Vlad
--
Firebird-Devel mailing lis
On 11/13/2015 01:17 PM, Vlad Khorsun wrote:
> 13.11.2015 11:21, Alex Peshkoff wrote:
>
>>> So the prototype will become:
>>>
>>> void FB_PLUGIN_ENTRY_POINT(IStatus*, IPluginInitialization*);
>> OK, let's pass here more generic interface. Though currently I do not
>> see something except getMaster()
Flamerobin ;-)
from ISQL
2.5
Current memory = 1095865152
Delta memory = 24
Max memory = 1161811608
Elapsed time= 0.41 sec
Buffers = 65536
Reads = 0
Writes 0
Fetches = 91
3.0
Current memory = 1121098560
Delta memory = 0
Max memory = 1191224776
Elapsed time= 0.298 sec
Buffers = 65536
Reads = 0
Wr
13.11.2015 11:21, Alex Peshkoff wrote:
>> So the prototype will become:
>>
>> void FB_PLUGIN_ENTRY_POINT(IStatus*, IPluginInitialization*);
>
> OK, let's pass here more generic interface. Though currently I do not
> see something except getMaster() in it - let's be generic.
There is PluginModu
On 11/13/2015 12:57 PM, Vlad Khorsun wrote:
> 13.11.2015 11:45, Adriano dos Santos Fernandes wrote:
>> On 12/11/2015 17:18, Vlad Khorsun wrote:
>>> 12.11.2015 20:24, Adriano dos Santos Fernandes wrote:
>>> ...
BTW, another info the plugin entry point could receive now: the library
filenam
Karol,
> 0 fetches, 0 marks, 0 reads, 0 writes.
Something is surely wrong with your tool 😉
Please try with ISQL.
Dmitry--
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/list
13.11.2015 11:45, Adriano dos Santos Fernandes wrote:
> On 12/11/2015 17:18, Vlad Khorsun wrote:
>> 12.11.2015 20:24, Adriano dos Santos Fernandes wrote:
>> ...
>>> BTW, another info the plugin entry point could receive now: the library
>>> filename.
>>>
>>> This way it can load additional configur
On 12/11/2015 17:18, Vlad Khorsun wrote:
> 12.11.2015 20:24, Adriano dos Santos Fernandes wrote:
> ...
>> BTW, another info the plugin entry point could receive now: the library
>> filename.
>>
>> This way it can load additional configuration files, for example.
>>
>> That can be obtained by it him
13.11.2015 11:21, Alex Peshkoff wrote:
>> Maybe they should be returned to the user, and a method to log things is
>> also necessary, but that probably should live in IMaster/IUtil
>
> Yes. We need an analogue of gds__log in IUtil.
Please. We need dedicated interface for logging and implementa
same for FB2.5 and FB3.0
IXA_WPLATA__KONTRAHENT__PK DYR_ID 0.07
IXA_WPLATA__KONTRAHENT__PK WPLATA_KONTRAHENT_ID 0.31
WPLATA_PK DYR_ID 0.058824
WPLATA_PK INSP_ID
On 11/12/2015 06:20 PM, Adriano dos Santos Fernandes wrote:
> Hi!
>
> Currently plugin entry points receives just an IMaster.
>
> It cannot do much things with only this.
>
> Not all plugins will register a factory and do all the work lazily.
If plugin does not register a factory error loading it
Karol,
> CREATE INDEX IXA_WPLATA__KONTRAHENT__PK ON WPLATA
> (WPLATA_KONTRAHENT_ID,DYR_ID);
> statistics both 0.07
> CONSTRAINT WPLATA_PK PRIMARY KEY
> (DYR_ID)
> statistics both 0.00
Please provide the result for:
select rdb$index_name, rdb$field_name, rdb$statistics
f
26 matches
Mail list logo