home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.databases:7783 comp.databases.ingres:1861
- Newsgroups: comp.databases,comp.databases.ingres
- Path: sparky!uunet!destroyer!sol.ctr.columbia.edu!usenet.ucs.indiana.edu!fractal!mdchaney
- From: mdchaney@fractal.ucs.indiana.edu (M Darrin Chaney)
- Subject: Re: Ingres questions followup
- Message-ID: <BxLBKH.2w0@usenet.ucs.indiana.edu>
- Sender: news@usenet.ucs.indiana.edu (USENET News System)
- Nntp-Posting-Host: fractal.ucs.indiana.edu
- Organization: Indiana University, Bloomington
- References: <11NOV199216120229@stars.gsfc.nasa.gov>
- Distribution: usa
- Date: Thu, 12 Nov 1992 06:33:53 GMT
- Lines: 24
-
- thompson@stars.gsfc.nasa.gov (William Thompson, code 682.1, x2040) writes:
- >Nobody could think of any concerns involved with importing/exporting text
- >files. I take this to mean that ASCII I/O is also restricted to ~2000
- >characters per line, but that there are no additional restrictions.
-
- Actually, that's not true. You assume that the size of the field in the
- database is the same as its textual size. A four byte integer can consume
- 9 or 10 ascii characters. You get the drift.
-
- >It appears
- >that this is true even on VAX machines, where text files have traditionally
- >been restricted to 255 characters per line.
-
- Traditionally, files under VMS are limited to 65534 byte records. That's
- because for normal variable length record files, the record length is stored
- in the two bytes before the record. For Stream-LF files, that barrier can
- be overcome.
-
- Darrin
- --
-
- mdchaney@iubacs mdchaney@bronze.ucs.indiana.edu mdchaney@rose.ucs.indiana.edu
-
- "I want- I need- to live, to see it all..."
-