Re: SQL-inconsistent results using XMLELEMENT, XMLSERIALIZE, XMLCONCAT -- MIDRANGE-L

Subject: Re: SQL-inconsistent results using XMLELEMENT, XMLSERIALIZE, XMLCONCAT
From: Ken Sims <mdrg8066@xxxxxxxxxxx>
Date: Tue, 09 Jul 2013 13:21:54 -0700
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Hi Steve -

On Tue, 9 Jul 2013 15:11:13 +0000, "Needles,Stephen J"
<SNEEDLES@xxxxxxxxxxxxxxxx> wrote:

When I run it, I get the following results in parm_xml1:

<XMLGROUP><action>get</action><contractNumber>1234567890</contractNumber></XMLGROUP>

When another runs it, this is the result:

<XMLGROUP><action>h4Wj</action><contractNumber>8fLz9PX29/j58A==</contractNumber></XMLGROUP>

Without actually verifying it, my first impression is that those
values in the second result are base64 encoded.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.