[Firebird-devel] Details on Firebird 3 protocol 13 changes, authentication and encryption
I am getting to a point where I want to implement the protocol 13 and new authentication and encryption of Firebird 3 in Jaybird. I'd like to know what was changed for protocol 13, and details on how authentication and encryption work, and how I can implement it. I'd prefer a formal description without having to dig and interpret the sources, but I assume that is a pipe dream. So if nor formal documentation is available, then pointers to specific source code/methods would be appreciated. Mark -- Mark Rotteveel -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] Preventing error code "collision"
Up to now Jaybird has always used the Firebird error codes, or specific error messages defined in code. I am currently looking into defining some Jaybird specific error codes, with associated messages and SQL states. To prevent collisions with future error codes in Firebird, I'd like to know if using codes below 3 would be sufficient to prevent collision, or would it be better to follow the same formal rules as used inside Firebird to generate error codes (eg reserve a facility code for Jaybird)? Mark -- Mark Rotteveel -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Preventing error code "collision"
25.07.2015 14:57, Mark Rotteveel wrote: > Up to now Jaybird has always used the Firebird error codes, or specific > error messages defined in code. > > I am currently looking into defining some Jaybird specific error codes, > with associated messages and SQL states. Are you going to report is using Firebird API ? Are you going to add Jaybird specific messages into firebird.msg ? > To prevent collisions with > future error codes in Firebird, I'd like to know if using codes below > 3 would be sufficient to prevent collision, or would it be > better to follow the same formal rules as used inside Firebird to > generate error codes (eg reserve a facility code for Jaybird)? I think, facility is what you need. Regards, Vlad -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Preventing error code "collision"
25.07.2015 15:16, Vlad Khorsun wrote: >> To prevent collisions with >> future error codes in Firebird, I'd like to know if using codes below >> 3 would be sufficient to prevent collision, or would it be >> better to follow the same formal rules as used inside Firebird to >> generate error codes (eg reserve a facility code for Jaybird)? > > I think, facility is what you need. I second that. Dmitry -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Preventing error code "collision"
On 25-7-2015 14:16, Vlad Khorsun wrote: > 25.07.2015 14:57, Mark Rotteveel wrote: >> Up to now Jaybird has always used the Firebird error codes, or specific >> error messages defined in code. >> >> I am currently looking into defining some Jaybird specific error codes, >> with associated messages and SQL states. > > Are you going to report is using Firebird API ? Are you going to add > Jaybird specific messages into firebird.msg ? Jaybird doesn't use firebird.msg, I occasionally export the error messages and sqlstates from a Firebird build to the isc_error_msg.properties and isc_error_sqlstates.properties of Jaybird (and the error code constants to ISCConstants.java). However, the Jaybird specific error codes, error messages and sqlstate mapping will be within Jaybird itself. I want to reuse (extend) the existing error message mechanism inside Jaybird to obtain the messages and sqlstate mappings from multiple sources and that means that I have to avoid collisions. >> To prevent collisions with >> future error codes in Firebird, I'd like to know if using codes below >> 3 would be sufficient to prevent collision, or would it be >> better to follow the same formal rules as used inside Firebird to >> generate error codes (eg reserve a facility code for Jaybird)? > > I think, facility is what you need. How would I go about that if none of the errors in that facility are defined inside Firebird, and how can I know/calculate the range of error codes I can use (a quick glance at the code seems to suggest that each facility has 24 bits for error codes)? Mark -- Mark Rotteveel -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
[Firebird-devel] Windows snapshots builds broken?
The last snapshot build for Windows is dated 16-July. []s Carlos http://www.firebirdnews.org FireBase - http://www.FireBase.com.br -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Windows snapshots builds broken?
On 25-7-2015 15:00, Carlos H. Cantu wrote: > The last snapshot build for Windows is dated 16-July. That happens to be the day of the SourceForge storage failure, and Subversion is still offline so no new code has been written since then. I don't think it is a coincidence. Mark -- Mark Rotteveel -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
Re: [Firebird-devel] Preventing error code "collision"
25.07.2015 15:45, Mark Rotteveel wrote: > > How would I go about that if none of the errors in that facility are > defined inside Firebird, We could define and reserve facility code for Jaybird and let you know it. > and how can I know/calculate the range of error > codes I can use (a quick glance at the code seems to suggest that each > facility has 24 bits for error codes)? Look at src\common\msg_encode.h : const ISC_STATUS ISC_MASK = 0x1400; // Defines the code as a valid ISC code const ISC_STATUS FAC_MASK = 0x00FF; // Specifies the facility where the code is located const ISC_STATUS CODE_MASK = 0x; // Specifies the code in the message file const ISC_STATUS CLASS_MASK = 0xF000; // Defines the code as warning, error, info, or other Hope it helps, Vlad -- Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
