| Subject | Re: A limitation of Firebird |
|---|---|
| Author | Ann Harrison |
| Post date | 2012-01-07T21:29:57Z |
On Sat, Jan 7, 2012 at 7:54 AM, mcastro171164 <mcastro171164@...> wrote:
Firebird's internal memory allocation and block management use 16 bit
values to describe the size of blocks. That limitation shows up in a
variety of ways - maximum record size, the "internal block size
exceeded" message when the compiler scratch block overflows, etc. As
recently as ten years ago, those restrictions were not very limiting,
but now they're hit regularly. The solution is a complete overhaul of
Firebird, moving to 32 or 64 bit sizes. That's a lot of work.
Best regards,
Ann
> Hello,You're right, but the problem is less simple than you may realize.
>
> This sugestion is addressed to the Dot.Net provider forum, not to this forum. Sorry.
>
> Anyway, I think that the Firebird mantainers should consider raising the limit of 64K bytes as the maximum size of a Firebird SQL query. Huge databases and Dot.Net ORM reachs this limitation very easily.
>
Firebird's internal memory allocation and block management use 16 bit
values to describe the size of blocks. That limitation shows up in a
variety of ways - maximum record size, the "internal block size
exceeded" message when the compiler scratch block overflows, etc. As
recently as ten years ago, those restrictions were not very limiting,
but now they're hit regularly. The solution is a complete overhaul of
Firebird, moving to 32 or 64 bit sizes. That's a lot of work.
Best regards,
Ann