Traditionally WHEN is an output limiter and WITH is a selector, so they occupy
different branches of the process. But with a SELECT SAVING that difference
becomes blurred, so I would vote for a WHEN to be allowed in that case.
Of course on unidata it would no doubt have to be on some dumb UDT.OP
You can already return record ids with a SELECT that have some multi-value
which matches, just by using the WITH command.
-Original Message-
From: Jeffrey Butera
To: u2-users
Sent: Fri, Mar 8, 2013 12:49 pm
Subject: Re: [U2] Unidata WHEN/ASSOCIATED
On 03/08/2013 03:47 PM
g.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeffrey Butera
Sent: Friday, March 08, 2013 1:23 PM
To: U2 Users List
Subject: [U2] Unidata WHEN/ASSOCIATED
Stupid question: is there a good reason why WHEN/ASSOCIATED can only be used
with LIST and not SELECT?
--
Jeffrey Butera, PhD
Asso
vid A. Green
(480) 813-1725
DAG Consulting
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeffrey Butera
Sent: Friday, March 08, 2013 1:23 PM
To: U2 Users List
Subject: [U2] Unidata WHEN/ASSOCIATED
Stupid question: is th
Stupid question: is there a good reason why WHEN/ASSOCIATED can only be
used with LIST and not SELECT?
--
Jeffrey Butera, PhD
Associate Director for Applications and Web Services
Information Technology
Hampshire College
413-559-5556
http://www.hampshire.edu
http://www.facebook.com/hampshirecoll
