home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!murphy!dwrsun4!perl
- From: perl@dwrsun4.UUCP (Robert Perlberg)
- Newsgroups: comp.databases.ingres
- Subject: Re: Ingres Design Limits
- Message-ID: <2967@perl-sun.dwrsun4.UUCP>
- Date: 22 Dec 92 21:44:26 GMT
- References: <1992Dec9.235410.4228@goethe.credtech.com>
- Organization: Dean Witter Reynolds Inc., New York
- Lines: 35
-
- In article <1992Dec9.235410.4228@goethe.credtech.com>, twombly@goethe.credtech.com (chris twombly) writes:
- > I have heard that INGRES has some limitations, and amongst them:
- >
- > - 30 table limit per database
-
- Definitely false. I've have databases with many more tables than
- that. Where did you get that from?
-
- > - 2000 byte limit record size
-
- True. This also extends to joins. The rows produced by a SELECT
- cannot be more that 2000 bytes worth of data each, so you can't do
- something like this:
-
- create table t1 (k1 integer, c1 char(1500));
- create table t2 (k2 integer, c2 char(1500));
-
- select c1, c2 from t1, t2 where k1 = k2;
-
- The select will complain about the resulting row being too long, even
- if you are not redirecting the output into another table.
-
- > - 256 column limit per table
-
- Probably true. I've run into the 2000 byte limit myself (although if I
- had my way I would have designed the database differently), but I'd
- like to know what type of application would need more than 256
- columns.
-
- Robert Perlberg
- Dean Witter Reynolds Inc., New York
- dwrsun4!perl@murphy.com -or- philabs!dwrsun4!perl
-
- "We don't believe the software industry is ripping off the customer."
- -- Ken Wasch, executive director of the Software Publishers Association
-