pg.ddx.ioUniversity INGRES on Usenet (1985-1995): threads about Berkeley INGRES, QUEL and EQUEL from comp.databases.ingres, comp.databases and net.database
From: gainer@gainer.engr.sgi.com
Subject: Re: VARCHAR, WHY THE 2000 Character Limit ??
Date: 1995/11/29
Message-ID: <49i118$bo7@fido.asd.sgi.com> (raw)
References: <49794h$pof@carbon.cudenver.edu>
<Pine.SOL.3.91.951129105036.782A-100000@iglou>
In article <Pine.SOL.3.91.951129105036.782A-100000@iglou>,
Lucky Leavell <ris@iglou.com> wrote:
>On Sat, 25 Nov 1995, George/Jorge wrote:
>
>> Has anyone wondered why varchar/varchar2 has this magical limit of 2000
>> characters? Well I have, this limit seems to exist in two databases that
>> I have used, namely ORACLE and INGRES. I have looked around for documentation
>> to determine if this is a SQL standard but I haven't found anything.
>>
>>
>I believe the Ingres limit comes from their use of a page size of 2048
>bytes. Removing the 48 bytes used by the RDBMS engine, leaves 2000
>bytes. OpenIngres does add, among others, two new data types:
>
> long byte - up to 2 GB of binary data
> long varchar - up to 2GB of character data
>
>Perhaps the next question is: why did Ingres use the 2K page size instead
>of, say, 4K or 8K? I don't know; ask Michael Stonebraker, et al.
I am curious about the "long byte" support you mentioned. To what degree are
long byte types available for use in SQL statements? What sorts of operations
may be performed on them? Are they very useful? Or are they there just to
check off the "BLOB support" box?
Pat