> On Nov 17, 2019, at 6:22 AM, jerz...@o2.pl [firebird-support] > <firebird-support@yahoogroups.com> wrote: > > On Sat, 16 Nov 2019 10:29:44 +0100, Mark Rotteveel m...@lawinegevaar.nl > [firebird-support] wrote: > >>>> In Release Notes for these versions. >>>> Maximum size of record was not changed. > > >>> This is a very big limitation, a few larger char fields with multibyte >>> coding and we get an exception. I don't understand why this limitation >>> hasn't been removed. > >> Because it is hard to do. A lot of internals in Firebird and its clients >> rely on this maximum size (hint: the number itself fits in a 2-byte >> unsigned integer). It is not like you just need to update a MAX_ROW_SIZE >> constant and it is changed. > > I understand it's not trivial. But that's why there are new versions like 3, > 4 or now 5 to avoid such limitations. > >> Consider that PostgreSQL has a limit of around 8KB (with its default >> page size). However, PostgreSQL has the advantage that variable length >> fields can be automatically stored out-of-line (ie basically as a blob, >> but that is transparent to the user).
Perhaps a better solution for Firebird would be a similar text type that holds arbitrary length strings. > > However, according to the documentation "row size" is much larger. But maybe > I am misreading this information. > > https://wiki.postgresql.org/wiki/FAQ#What_is_the_maximum_size_for_a_row.2C_a_table.2C_and_a_database.3F > > -- > kind regards > jerzy > > > > ------------------------------------ > Posted by: jerz...@o2.pl > ------------------------------------ > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Visit http://www.firebirdsql.org and click the Documentation item > on the main (top) menu. Try FAQ and other links from the left-side menu > there. > > Also search the knowledgebases at > http://www.ibphoenix.com/resources/documents/ > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > ------------------------------------ > > Yahoo Groups Links > > >
