I'm currently writing a driver for the R2DBC specification (a new Java
specification for reactive database drivers). Is it OK if I reserve a
new facility code for R2DBC driver errors (similar like I did in the
past for Jaybird)?
Mark
--
Mark Rotteveel
Firebird-Devel mailing list, web
On 11/26/20 12:05 PM, Alex Peshkoff via Firebird-devel wrote:
Useally we do not log DEV_BUILD problems (first of all not to confuse
users I think), I will take a look what's wrong.
fixed
Firebird-Devel mailing list, web interface at
On 11/26/20 11:15 AM, Paul Reeves wrote:
When I build HEAD with --enable-developer and -DUSE_VALGRIND I get
these errors:
alloc.cpp:2182:79: error: invalid conversion from ‘size_t (*)(size_t) {aka
long unsigned int (*)(long unsigned int)}’ to ‘unsigned int’ [-fpermissive]
common.h:772:51:
When I build HEAD with --enable-developer and -DUSE_VALGRIND I get
these errors:
alloc.cpp:2182:79: error: invalid conversion from ‘size_t (*)(size_t) {aka
long unsigned int (*)(long unsigned int)}’ to ‘unsigned int’ [-fpermissive]
common.h:772:51: error: invalid operands of types ‘size_t
