Re: [U2] dynamically disassociate associated fields?

2011-04-01 Thread Wols Lists
On 01/04/11 02:36, Hona, David wrote: > You can use an alternate dictionary in native or SQL queries... > > USING DICT MYALTDICT > > Or more practical suggest made by Kate is to have a different dictionary > definition... > The problem with Kate's idea is that it makes each column its own table

Re: [U2] dynamically disassociate associated fields?

2011-03-31 Thread Hona, David
Behalf Of Shane Ricciardi Sent: Thursday, 31 March 2011 4:22 AM To: u2-users@listserver.u2ug.org Subject: [U2] dynamically disassociate associated fields? Hello. I have a rather large MV association that contains around 40 or so I- type dicts that all call subroutines. Since this is essentially a

Re: [U2] dynamically disassociate associated fields?

2011-03-31 Thread rayw
Two ways Dynamic Normalization SELECT colname1,colname2,colname3 FROM tablename_assocname; Using this method only the primary key (@ID) and columns named in the association can be selected. UNNEST Operator SELECT colname1,colname2,colname3 FROM UNNEST tablename ON assocname; Using this meth

Re: [U2] dynamically disassociate associated fields?

2011-03-31 Thread Kate Stanton
Another DICT item with blank association? On 31 March 2011 06:22, Shane Ricciardi wrote: > Hello. I have a rather large MV association that contains around 40 or so I- > type dicts that all call subroutines. Since this is essentially a "subtable" > to > uv/SQL, selecting any field from the subta

[U2] dynamically disassociate associated fields?

2011-03-30 Thread Shane Ricciardi
Hello. I have a rather large MV association that contains around 40 or so I- type dicts that all call subroutines. Since this is essentially a "subtable" to uv/SQL, selecting any field from the subtable causes all the fields to be processed, although only the requested field is returned. As you c