Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!nike!ucbcad!ucbvax!hplabs!oracle!bradbury
From: bradbury@oracle.UUCP (Robert Bradbury)
Newsgroups: net.database
Subject: Re: Ingres text fields (was: Re: speed of ORACLE, large INFORMIX DBMS's)
Message-ID: <458@oracle.UUCP>
Date: Mon, 21-Jul-86 16:09:45 EDT
Article-I.D.: oracle.458
Posted: Mon Jul 21 16:09:45 1986
Date-Received: Mon, 28-Jul-86 00:52:11 EDT
References: <449@oracle.UUCP> <235@hdsvx1.UUCP> <590@bcsaic.UUCP>
Organization: ORACLE Corporation, 20 Davis Dr., Belmont CA 94002
Lines: 19
Summary: Long text strings.

In article <590@bcsaic.UUCP>, michaelm@bcsaic.UUCP (michael maxwell) writes:
> 
> Long text strings?  I've wanted that... Our documentation (dated Dec. 1977!)
> says that a tuple can only be 498 bytes (512 byte pages - overhead), so a text
> field could only be 498 bytes long (and then only if you were willing to limit
> yourself to one text field in the tuple, clearly not a practical situation).
> The version of Ingres we (are going to) use is quite a bit more recent than
> that (I don't have the date right here); it is a "public domain" version, not
> the commercially available version.  Has the 498 byte limit been overcome 
> in more recent versions of Ingres?

In the commercial version of Ingres I'm pretty sure they use 2K data blocks
and allow longer strings.  (Or you could use the RAW datatype in Oracle
and get up to 65K bytes in a row).

-- 
Robert Bradbury
Oracle Corporation
(206) 364-1442                            {ihnp4!muuxl,hplabs}!oracle!bradbury