I believe the SAVING UNIQUE operating on a multivalued field
treats the request as a BY.EXP request...thus giving you the
value marks.
You might want to try BSELECT to get just the individual keys:
SELECT PERSON.ST 3152749
BSELECT PERSON.ST PST.ROOM.ASSIGNMENTS
SAVE.LIST X.1
[EMAIL
it looks like PST.ROOM.ASSIGNMENT is multivalued and used for other things
other then just storing the room# ???
what does the dict PST.ROOM.ASSIGNMENTS look like ? is it defining the
entire attribute ?
if you just want the 1'st value, create a dict item defining it and select
saving unique new
Date: 23 Aug 2004 16:26:54 -0300
From: Philippe Parent [EMAIL PROTECTED]
...
(where 'y' is the value marker)
Why is there y1y1, y2y1, y3y1 appended at the end of
each ID? I'm guessing it has to do with the saving
unique feature or something?
...
So first, what is the extraneous
Yeah, the BSELECT works, I'm using it as an alternative... I just like
to ensure to remove duplicates too which is why I was using SAVING
UNIQUE. I was just wondering why the value marks... And the thing is
that its only when using LIST.ALGEBRA that I found a problem with this.
If you just do a
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, August 24, 2004 5:55 AM
To: [EMAIL PROTECTED]
Subject: Re: [U2] UNIDATA - SAVING UNIQUE and LIST.ALGEBRA
Date: 23 Aug 2004 16:26:54 -0300
From: Philippe Parent [EMAIL PROTECTED]
...
(where 'y' is the value marker
produce a SAVEDLISTS record with one ROOM.ASSIGNMENT.ID per
attribute.
-Original Message-
From: Philippe Parent [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 24, 2004 9:48 AM
To: [EMAIL PROTECTED]
Subject: RE: [U2] UNIDATA - SAVING UNIQUE and LIST.ALGEBRA
I checked the dict and AE'd a few
Check out the documentation for READNEXT its the same feature in
universe... least it looks it to me.
At 03:26 PM 8/23/2004, you wrote:
Hi all,
Not a regular here but I was hoping someone could enlighten me with this
interesting 'feature' of UNIDATA...
If I issue a select statement using
