Re: [Firebird-devel] isc_info_firebird_version response format

2016-06-22 Thread Dmitry Yemanov
22.06.2016 10:28, Jiří Činčura wrote: >> And this may be considered a bug :-) given that InterBase returns two >> strings for this tag. > > Do you want me to put to tracker? Let's see what others think. This is really a low priority thing. Dmitry

Re: [Firebird-devel] isc_info_firebird_version response format

2016-06-22 Thread Jiří Činčura
> And this may be considered a bug :-) given that InterBase returns two > strings for this tag. Do you want me to put to tracker? Here's again raw bytes for that tag. It's really just one message. [0]: 12 [1]: 30 [2]: 0 [3]: 1 [4]: 28 [5]: 87 [6]: 73 [7]: 45

Re: [Firebird-devel] isc_info_firebird_version response format

2016-06-22 Thread Dmitry Yemanov
22.06.2016 09:57, Jiří Činčura wrote: > I was just confused by isc_info_isc_version having > just one. And this may be considered a bug :-) given that InterBase returns two strings for this tag. AFAIU, in the old days we've just replaced isc_info_isc_version with isc_info_firebird_version in

Re: [Firebird-devel] isc_info_firebird_version response format

2016-06-22 Thread Jiří Činčura
OK, so it's expected. I was just confused by isc_info_isc_version having just one. I'll adjust it in the provider. -- Mgr. Jiří Činčura Independent IT Specialist -- Attend Shape: An AT Tech Expo July 15-16. Meet us at

Re: [Firebird-devel] isc_info_firebird_version response format

2016-06-22 Thread Dmitry Yemanov
21.06.2016 22:45, Jiří Činčura wrote: > I'm sending the isc_info_firebird_version, isc_info_end only in > op_info_database. And the buffer I get back is: > 103 isc_info_firebird_version > 74, 0, total length of the returned clumplet > 2, number of strings inside the clumplet > 28, 87, ...

Re: [Firebird-devel] isc_info_firebird_version response format

2016-06-21 Thread Jiří Činčura
> AFAIK, it's not. And I don't see how it can happen in the code. I'm sending the isc_info_firebird_version, isc_info_end only in op_info_database. And the buffer I get back is: 103, 74, 0, 2, 28, 87, 73, 45, 86, 51, 46, 48, 46, 48, 46, 51, 50, 52, 56, 51, 32, 70, 105, 114, 101, 98, 105, 114,

Re: [Firebird-devel] isc_info_firebird_version response format

2016-06-21 Thread Dimitry Sibiryakov
21.06.2016 19:58, Dmitry Yemanov wrote: > AFAIK, it's not. And I don't see how it can happen in the code. AFAIR, each layer adds its own version to the result, so it is engine version + Y-valve version or remote Y-valve + local Y-valve. -- WBR, SD.

Re: [Firebird-devel] isc_info_firebird_version response format

2016-06-21 Thread Dmitry Yemanov
21.06.2016 19:48, Jiří Činčura wrote: > > when I ask for isc_info_firebird_version (currently on FB3) it looks to > me I get response for isc_info_isc_version followed by > isc_info_firebird_version together. Is that expected? AFAIK, it's not. And I don't see how it can happen in the code.

[Firebird-devel] isc_info_firebird_version response format

2016-06-21 Thread Jiří Činčura
Hi *, when I ask for isc_info_firebird_version (currently on FB3) it looks to me I get response for isc_info_isc_version followed by isc_info_firebird_version together. Is that expected? Maybe it was some compatibility shim. I.e. for isc_info_firebird_version on FB3: length: 76 manually