pg.ddx.io  University INGRES on Usenet (1985-1995): threads about Berkeley INGRES, QUEL and EQUEL from comp.databases.ingres, comp.databases and net.database  
help / color / mirror / Atom feed
From: pbrown@triplerock.CS.Berkeley.EDU
Subject: Re: VARCHAR, WHY THE 2000 Character Limit ??
Date: 1995/11/27
Message-ID: <49d6uv$2pe@agate.berkeley.edu> (raw)
References: <49794h$pof@carbon.cudenver.edu>

George/Jorge (ghharrac@ouray.cudenver.edu) 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.

  This is related to the physical limitations of the underlying page
 size. All data in these Relational Products must fit onto a data
 page, because their locking and logging systems are page-oriented.
 Not a bad thing, just one of the trade-off decisions you need to make.
 Check out Date or Ullman for a rounded treatment of why pages are considered
 so important.

  Informix uses a flexible page size approach to this problem, but my
 guess is that even it doesn't deal with megabyte documents.   
 
  Hope is at hand however. Extensible DBMS's allow you to store documents
 of arbitrary length as attributes of the table. Check out the usual
 suspects to see where this is headed (Object Foo Inc, UniSQL, O2, Illustra)
 and be mindful that all of the capital-R vendors are working towards
 this type of extension.

--
  =====================================================================
     Paul Brown                                     ^..^
     pbrown@postgres.Berkeley.EDU                   (oo)  -  Oink!
     #include <std_disclaimer.h>
            "Think global - act loco!" - Zippy the Pinhead
  =====================================================================








view thread (17+ messages)  latest in thread

Message-ID: <49d6uv$2pe@agate.berkeley.edu>
Permalink:  ../49d6uv$2pe@agate.berkeley.edu/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox