Brian
The generated XML did include both nodes as shown in my example.
using 10.1 gives
... etc
using 10.2.7 gives only one of the nodes
... etc
I would have been happy to lose the node but not the
node defining the item within the file.
Have we found a bug where the wrong one h
Jeffrey,
I've found that WHEN, instead of WITH, is better at limiting the values
returned to a select.
i.e. SELECT FILE WHEN FIELD UNLIKE "SF..." OR WHEN FIELD UNLIKE "SH..."
Andrew
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey Butera
Sent: S
I experimented with it and got much closer with:
SELECT FILE WITH EVERY FIELD UNLIKE "SF..." AND WITH EVERY FIELD UNLIKE
"SH...
It is not quite what you want but much closer.
> From: [EMAIL PROTECTED]
> To: u2-users@listserver.u2ug.org
> Subject: [U2] Friday query logic
> Date: Fri, 20 Jun 2008 1
Can you do a SELECT to select the ones WITH EVERY FIELD LIKE "SF..." "SH..."
and then do NSELECT to select the inverse set?
> - Original Message -
> From: "Jeffrey Butera" <[EMAIL PROTECTED]>
> To: u2-users@listserver.u2ug.org
> Subject: [U2] Friday query logic
> Date: Fri, 20 Jun 2008 11
Sara
Did you get BOTH REF.CODES_XML and TABLE_GENDER nodes? I would have expected
the AS to override the REF.CODES_XML node, in which case you might be able to
get it back by using an XMLMAPPING file. If not, I'm confused ...
Brian
We have just migrated from UV 10.1 to UV 10.2.7 and found we
We have just migrated from UV 10.1 to UV 10.2.7 and found we get
different results from a query producing XML. Unfortunately we have
built our consuming client around the desirable original behaviour, but
fortunately this project is not yet in production. Does anyone know how
we can get this beha
