Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!tank!dwayne@rover.bsd.uchicago.edu
From: dwayne@rover.bsd.uchicago.edu
Newsgroups: comp.databases
Subject: Re: Ingres is making me mad!!
Message-ID: <1979@tank.uchicago.edu>
Date: 23 Feb 89 17:34:34 GMT
Sender: news@tank.uchicago.edu
Organization: University of Chicago - Biomedical Physics
Lines: 25

I wrote
>>Well, I hit that legendary boundary of 127 columns in a table
>>does anybody have any ideas that might help me get around
>>this (I think undocumented) limitation [without breaking into tables]???

I guess I didn't make myself very clear in my original posting.

The problem is that there appears to be a ** 126 ** column limit, count
it, not 127 on retrieves and modifies in QBF.  According to RTI this
is indeed correct and there not much someone can do about it.  However,
word has it that 6.0 will have higher limits all around.  My answer is to
delete yet another field off of my form (I started with 200+ fields).

Again, my reason for leaving the data in one table (as you medical guys
surely know) is because in clinical environments nobody knows what will
potentially be interesting.  They want to have the ability to do quick and
dirty queries on whatever seems publishable that day.  Our physicians would
have neither the time nor the inclination to learn/use SQL/QUEL.

Certainly a questionnaire type study is not the best use for a relational
database.  But for creating a form with which they can logically query
the data with out much instruction, it is a nice, quick solution.

Dwayne Spradlin
dwayne@rover.bsd.uchicago.edu