Re: [U2] [UV] Marking New Index as Built
Thinking back to Prime INFORMATION, that was the default behaviour. You could have deferred updates pending and still have new transactions update the indexes. But, then, in Prime INFORMATION BUILD.INDEX and UPDATE.INDEX were two separate commands, unlike the UniVerse implementation. There's probably something you could tweak in the INDEX.MAP file to get this to work. Unfortunately I am in an airport lounge (again!) and not carrying my UniVerse Internals training class notes. = ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] dynamically disassociate associated fields?
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 method (which is akin to BY.EXP in the other query language TCL) you can select any columns whether from the base table (in which case they'll be repeated) or from the assocation. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UniVerse/SQL: This EVAL field requires a qualifying file name
It does wherever the column reference is or may be ambiguous (or wherever the query parser assumes it may be ambiguous!). Try this. SELECT A.field1, B.field2, EVAL B.'TESTING' AS field3 FROM table1 A, table2 B WHERE A.KeyField = B.KeyField; -Original Message- From: Shane Ricciardi shane...@optonline.net To: u2-users@listserver.u2ug.org Sent: Wed, Feb 16, 2011 2:52 am Subject: [U2] UniVerse/SQL: This EVAL field requires a qualifying file name Anyone ever see this error? It's happening with a SQL statement that pulls data rom a table and a subtable, which is just an association. Something like his: ELECT field1,B.field2,EVAL 'TESTING' AS field3 FROM table1,table1_wtvr B WHERE able1.KeyField = B.KeyField; Thanks. ___ 2-Users mailing list 2-us...@listserver.u2ug.org ttp://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] U2U Australia
I'm now registered. See youse all there! ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] [UV] How to return 'column' from dyn array?
Just a thought; does FIELDS work? I doubt that version 1 will work, but version 2 certainly will. Version 1 FIELDS(dynarray, @VM, 3, 1) Version 2 FIELDS(CONVERT(@VM,|,dynarray), |, 3, 1) - Original Message - From: Barry Brevik [EMAIL PROTECTED] Date: Wed, 18 Aug 2004 13:40:54 -0700 To: U2-users (E-mail) [EMAIL PROTECTED] Subject: [U2] [UV] How to return 'column' from dyn array? I just realized that there seems to be no function for the following situation. Given the dynamic array: 10 @vm 20 @vm 30 @FM 11 @vm 21 @vm 31 @FM 12 @vm 22 @vm 32 ...I look at this as the fields being records, or rows, and the values being columns. I'd like a function that returns a dynamic array of just column 3, that is '30', '31' and '32'. Am I making sense? Is there something in UV basic that does this? Barry --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] EVAL formatting
I can't tell you exactly where it is in the manual, but you can use the same field modifiers (TOTAL, CALC, BREAK.ON, etc.) and field qualifiers (FMT, CONV, COL.HDG, AS, etc.) with EVAL as you can with named fields. Field qualifiers, in particular, override dictionary specifications for named fields, or supply them for EVAL expressions. AS gives the EVAL expression a field name that can be used elsewhere in the sentence. CONV specifies a conversion specification. COL.HDG specifies a column heading. Multi-line with 'L', e.g. COL.HDG Post'L'Code FMT specifies a formatting specification. SINGLE.VALUE specifies that the field will be treated as single-valued. MULTI.VALUE specifies that the field will be treated as multi-valued. ASSOC places the (multi-valued) field into an existing association. ASSOC.WITH places the (multi-valued) field into a temporary association with another multi-valued field. --- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/