Re: [Firebird-devel] isc_info_firebird_version response format
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 -- Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] isc_info_firebird_version response format
> 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 [8]: 86 [9]: 54 [10]: 46 [11]: 51 [12]: 46 [13]: 53 [14]: 46 [15]: 50 [16]: 54 [17]: 57 [18]: 53 [19]: 50 [20]: 32 [21]: 70 [22]: 105 [23]: 114 [24]: 101 [25]: 98 [26]: 105 [27]: 114 [28]: 100 [29]: 32 [30]: 50 [31]: 46 [32]: 53 [33]: 1 [34]: 0 ... -- Mgr. Jiří Činčura Independent IT Specialist -- Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] isc_info_firebird_version response format
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 /remote/merge.cpp while it could be more correct to handle both there. Dmitry -- Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] isc_info_firebird_version response format
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 AT Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] isc_info_firebird_version response format
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, ... length of the first string and the string itself > 43, 87, ... length of the second string and the string itself i.e. the output is a concatenation (kind of) of versions strings of all the routed providers, as Dimitry Sibiryakov said. In your case, this is the remote client provider and the engine provider. This happens only for the remote access. Embedded should return just one string (4th byte == 1, followed by 28, 87, ...). Dmitry -- Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] isc_info_firebird_version response format
> 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, 100, 32, 51, 46, 48, 43, 87, 73, 45, 86, 51, 46, 48, 46, 48, 46, 51, 50, 52, 56, 51, 32, 70, 105, 114, 101, 98, 105, 114, 100, 32, 51, 46, 48, 47, 116, 99, 112, 32, 40, 120, 50, 112, 99, 41, 47, 80, 49, 51, 1, 0, ... zeros to remaining 256. 103 is isc_info_firebird_version, looks OK to me. 28 should be the length of the message and following are the chars for "WI-V3.0.0.32483 Firebird 3.0" and so on. Am I parsing it wrong? 2.5.5 behaves the same way. -- Mgr. Jiří Činčura Independent IT Specialist -- Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] isc_info_firebird_version response format
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. -- Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] isc_info_firebird_version response format
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. Dmitry -- Attend Shape: An AT Tech Expo July 15-16. Meet us at AT Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
