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
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
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
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
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
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
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
