> > BTW, anybody remembers the reason why version 2 has two values -
> > isc_spb_version, isc_spb_current_version - at the beginning?
> >
>
> Sooner of all this should be asked in Borland / Inprise - that was so in
> IB6.0.
No obvious explanation but its the best you will get
On 7/20/21 5:17 PM, Jiří Činčura wrote:
BTW, anybody remembers the reason why version 2 has two values -
isc_spb_version, isc_spb_current_version - at the beginning?
Sooner of all this should be asked in Borland / Inprise - that was so in
IB6.0.
Firebird-Devel mailing list, web
BTW, anybody remembers the reason why version 2 has two values -
isc_spb_version, isc_spb_current_version - at the beginning?
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
> >> Aha! I suppose in version 2 I can't send data with 2-byte length, right?
> > Aka, I need to jump to version 3 and use 4-byte length.
> >
>
> Exactly.
> V.3 for SPB is like v.2 for DPB.
Thanks. Now I see the 2-byte length is only used for i.e. isc_info_svc_line.
--
Mgr. Jiří Činčura
On 7/20/21 4:52 PM, Jiří Činčura wrote:
Aha! I suppose in version 2 I can't send data with 2-byte length, right?
Aka, I need to jump to version 3 and use 4-byte length.
Exactly.
V.3 for SPB is like v.2 for DPB.
Firebird-Devel mailing list, web interface at
> Aha! I suppose in version 2 I can't send data with 2-byte length, right?
Aka, I need to jump to version 3 and use 4-byte length.
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
> Jiri, in order to use wide format you should use
> isc_spb_version3
> not
> isc_spb_version, isc_spb_current_version
> in the beginning (as a tag)
Aha! I suppose in version 2 I can't send data with 2-byte length, right?
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
On 7/20/21 4:29 PM, Jiří Činčura wrote:
Looks OK to me, but obviously it is not. Both the isc_spb_auth_plugin_name and
isc_spb_specific_auth_data should be wide
(https://github.com/FirebirdSQL/firebird/blob/B3_0_Release/src/common/classes/ClumpletReader.cpp#L324),
right? What am I missing?
Hi *,
I'm missing something obvious, probably because I was looking at these bytes
for too long. I constructed this SPB:
2, 2, 116, 3, 0, 0, 0, 83, 114, 112, 111, 0, 1, 0, 0, 68, 55, 57, 67, 56, 51,
52, 70, 66, 65, 49, 54, 67, 50, 54, 69, 50, 56, 53, 65, 67, 57, 69, 57, 50, 48,
57, 68, 65,
20.07.2021 14:50, Mark Rotteveel пишет:
According to the Firebird Language Reference[1], the
RDB$RELATION_FIELDS.RDB$UPDATE_FLAG signals whether a column is a
computed column (0) or a regular column (1) (or I guess, updatable (1)
vs not-updatable (0)).
Updatable vs non-updatable is correct.
According to the Firebird Language Reference[1], the
RDB$RELATION_FIELDS.RDB$UPDATE_FLAG signals whether a column is a
computed column (0) or a regular column (1) (or I guess, updatable (1)
vs not-updatable (0)). In practice, this doesn't seem to be the case
(see
Sehr geehrte Damen und Herren,
ich bin am heutigen Dienstag nicht im Büro zu erreichen.
Wenden Sie sich in dringenden Fällen gerne an off...@plugplant.de.
Grüße aus Börnsen,
Helge Schild
-
I am out of office today.
If it is
Hello,
I'm running into a similar error like the one described here:
https://www.mail-archive.com/firebird-support@yahoogroups.com/msg20295.html
Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to
allocate 206158430249 bytes) in /var/www/XXX/yyy.php on line 8
The Firebird
13 matches
Mail list logo
