Re: [Firebird-devel] Increasing CHAR/VARCHAR max. length to 64KB

2021-05-21 Thread Dimitry Sibiryakov
21.05.2021 14:49, Adriano dos Santos Fernandes wrote: On 21/05/2021 08:33, Dimitry Sibiryakov wrote: 21.05.2021 09:38, Alex Peshkoff via Firebird-devel wrote: Any idea how to avoid that?   Redeclare it as unsigned right now. Yes. But would be very bad to see not recompiled programs just

Re: [Firebird-devel] Increasing CHAR/VARCHAR max. length to 64KB

2021-05-21 Thread Adriano dos Santos Fernandes
On 21/05/2021 17:53, Alex Peshkoff via Firebird-devel wrote: > On 5/21/21 9:19 PM, Adriano dos Santos Fernandes wrote: > >>> And if we do change SQLDA_VERSION it's worth changing something else in >>> it. For example - make all sizes uint32, add separate field for charset, >>> may be something

Re: [Firebird-devel] Increasing CHAR/VARCHAR max. length to 64KB

2021-05-21 Thread Alex Peshkoff via Firebird-devel
On 5/21/21 9:19 PM, Adriano dos Santos Fernandes wrote: And if we do change SQLDA_VERSION it's worth changing something else in it. For example - make all sizes uint32, add separate field for charset, may be something else? My aim is to increase CHAR/VARCHAR lengths. I think there is no real

Re: [Firebird-devel] Increasing CHAR/VARCHAR max. length to 64KB

2021-05-21 Thread Alex Peshkoff via Firebird-devel
On 5/21/21 9:06 PM, Mark Rotteveel wrote: On 2021-05-21 16:51, Alex Peshkoff via Firebird-devel wrote: We have one more unused value for size - zero, we do not support characters with length == 0. We may store logical data length - 1, this will make it possible to have exactly 64Kb fields,

Re: [Firebird-devel] Increasing CHAR/VARCHAR max. length to 64KB

2021-05-21 Thread Leyne, Sean
> >> dsc_length is currently the descriptor's physical length. With the > >> change it will represent a logical length. To support that I added > >> getPhysicalLength() method to struct dsc returning an unsigned 32-bit > >> that sums +2/+1 for dtype_varying/dtype_cstring. > > > > During such

Re: [Firebird-devel] Increasing CHAR/VARCHAR max. length to 64KB

2021-05-21 Thread Adriano dos Santos Fernandes
On 21/05/2021 11:51, Alex Peshkoff via Firebird-devel wrote: > On 5/21/21 3:49 PM, Adriano dos Santos Fernandes wrote: >> On 21/05/2021 08:33, Dimitry Sibiryakov wrote: >>> 21.05.2021 09:38, Alex Peshkoff via Firebird-devel wrote: Any idea how to avoid that? >>>    Redeclare it as unsigned

Re: [Firebird-devel] Increasing CHAR/VARCHAR max. length to 64KB

2021-05-21 Thread Mark Rotteveel
On 2021-05-21 16:51, Alex Peshkoff via Firebird-devel wrote: We have one more unused value for size - zero, we do not support characters with length == 0. We may store logical data length - 1, this will make it possible to have exactly 64Kb fields, which (I believe) can be useful in some cases.

[Firebird-odbc-devel] Fatal Memory Error

2021-05-21 Thread Ken Hutchins
It was suggested that I build the drivers from source and delete the SQL*.h headers. I have done this. I have done this. I have reinstalled everything and tried multiple times. I still see the same Fatal Memory error that terrabytes of information are being requested when that is not

Re: [Firebird-devel] Duplicated boost in Windows v4 RC1 kits

2021-05-21 Thread Paul Reeves
On Fri, 21 May 2021 11:12:27 -0300 Adriano dos Santos Fernandes wrote: > Hi! > > In v4 RC1 zip kits for Windows, there is duplicated boost directory. > > One in include/firebird/impl/boost (correct) and another in > include/firebird/boost (incorrect). > I think I've located the cause of the

Re: [Firebird-devel] Increasing CHAR/VARCHAR max. length to 64KB

2021-05-21 Thread Dimitry Sibiryakov
21.05.2021 16:51, Alex Peshkoff via Firebird-devel wrote: We may store logical data length - 1, this will make it possible to have exactly 64Kb fields, which (I believe) can be useful in some cases. Yep, mess with varying::vary_length. -- WBR, SD. Firebird-Devel mailing list, web

Re: [Firebird-devel] Increasing CHAR/VARCHAR max. length to 64KB

2021-05-21 Thread Alex Peshkoff via Firebird-devel
On 5/21/21 3:49 PM, Adriano dos Santos Fernandes wrote: On 21/05/2021 08:33, Dimitry Sibiryakov wrote: 21.05.2021 09:38, Alex Peshkoff via Firebird-devel wrote: Any idea how to avoid that?   Redeclare it as unsigned right now. Yes. But would be very bad to see not recompiled programs just

Re: [Firebird-devel] Increasing CHAR/VARCHAR max. length to 64KB

2021-05-21 Thread Dimitry Sibiryakov
21.05.2021 14:49, Adriano dos Santos Fernandes wrote: So I think we must also create SQLDA_VERSION2 and raise error with length > 32767 with SQLDA_VERSION1. Creating of a new SQLDA version must be considered much deeper than just sqllen. -- WBR, SD. Firebird-Devel mailing list, web

[Firebird-devel] Duplicated boost in Windows v4 RC1 kits

2021-05-21 Thread Adriano dos Santos Fernandes
Hi! In v4 RC1 zip kits for Windows, there is duplicated boost directory. One in include/firebird/impl/boost (correct) and another in include/firebird/boost (incorrect). In recent GitHub actions artifacts, I see it's not there. But I don't see anything explicit in the logs since RC1, so I'm not

Re: [Firebird-devel] Increasing CHAR/VARCHAR max. length to 64KB

2021-05-21 Thread Adriano dos Santos Fernandes
On 21/05/2021 08:33, Dimitry Sibiryakov wrote: > 21.05.2021 09:38, Alex Peshkoff via Firebird-devel wrote: >> Any idea how to avoid that? > >   Redeclare it as unsigned right now. > Yes. But would be very bad to see not recompiled programs just crashing (or in infinite loop) if greater length

Re: [Firebird-devel] Increasing CHAR/VARCHAR max. length to 64KB

2021-05-21 Thread Dimitry Sibiryakov
21.05.2021 09:38, Alex Peshkoff via Firebird-devel wrote: Any idea how to avoid that? Redeclare it as unsigned right now. -- WBR, SD. Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel

Re: [Firebird-devel] Increasing CHAR/VARCHAR max. length to 64KB

2021-05-21 Thread Alex Peshkoff via Firebird-devel
On 5/20/21 5:32 PM, Adriano dos Santos Fernandes wrote: Hi! Currently max. CHAR length is limited to 32767 and max. VARCHAR to 32765. I didn't found any blocker prevent raising that limits to 65535 and 65533 respectively. Even not going into details agraid I see one serious problem - ISC API