Unidata 6.1.15 on AIX. The following command:
SSELECT SHOPPING.LIST BY.EXP PROD.NUM
Yields the message "too many values in sort". There is one record in this
file with 36,457 product numbers but would that "break" the BY.EXP? If so,
is there a config parameter somewhere that could be tweaked t
On our UniData 6.1 system:
:LIMIT
...
U_MAXBYEXPVAL: Number of values BY.EXP can handle = 10240.
...
According to HELP LIMIT:
The ECL LIMIT command displays maximum size limits for elements of UniData.
These limits are NOT CONFIGURABLE.
Larry Hiscock
Western Computer Services
-Origi
That's some shopping list.
I haven't seen anything anywhere that lets you adjust this limit.
Besides breaking the record up into separate tables, you may need to make a
temp file that normalizes this for you, by doing something like stringing the
value or row number into the key.
I've never ha
Agreed on all points. Will check this on my customer's system.
On Mon, Oct 25, 2010 at 9:11 AM, Dave Davis wrote:
> That's some shopping list.
>
> I haven't seen anything anywhere that lets you adjust this limit.
>
> Besides breaking the record up into separate tables, you may need to make a
> t
Of course, why would anyone need a BASIC program larger than 32K? I
believe it's called progress. Non-configurable size limits are just
__NOT__ acceptable in today's computing environment. The attendant
"work-arounds" are just plain ugly, and inexcusable.
The greatest aspect of PICK is the
Aging standards aside, I'd REALLY be questioning the design of a function
that uses multi-values approaching that number of items.I would think it
can't be very efficient...
Mike R.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2u
Mike:
You may be right, and I'd mostly think so too. However, now that I
spend most of my time in the web, I've often been wrong and am not
prescient enough to foresee everything. Data loads and unexpected
requirements often take me by surprise and I'd like to think that
Pick-like systems
I don't think UniVerse has the same limits (SELBUF controls in memory size)
but then UniVerse doesn't use the same structure as Unidata in their
selects.
Jerry Banker
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of B
Mike, I agree with you. This is unfortunately a vendor application and
they're storing quick retrieval lists of products. The customer can build
these lists (via Excel import) as big as they want.
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
h
If I were stuck with such a limitation, my approach might be to try an
replace that function with an 'outside the application' index or something.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King
Sent: Mond
I have recently been involved in a project that gave me my first chance to get
acquainted with the UV XDOM API functions.
I must say that I was bitterly disappointed with the documentation on the XML
functionality in UniVerse 10.2. Nothing more than a simple description of each
of the API func
Gregor, your comments serve as a testimonial to support my
position against using many of these vendor-supplied toolkits.
Some of them are OK, but many not. People insist on the DBMS
vendors building stuff for them, but then we get the mess that
you've described. For this reason I continue to rec
12 matches
Mail list logo