Sponsored Links
Sponsored Link

sponsored links

Collapse

Announcement

Collapse
No announcement yet.

Bug in xmlattributes() ?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Bug in xmlattributes() ?

    With xmlelement() and xmlforest(), if the tag value is a string literal, it is included as-is

    But with xmlattributes(), if the attribute value is a string literal, it is base64 encoded

    Is this correct? I would expect xmlattributes() to behave just like xmlelement() and xmlforest(), and do a base64 encode only if the value has ccsid 65535 (bit data)



  • #2
    Okay now I think it might be something else, because for some programs it's also happening for xmlelement() and xmlforest() values
    ProgramA, compiled from source in LibraryA/QRPGLESRC, string literals for xmlelement() are normal
    ProgramB, compiled from source in LibraryB/QRPGLESRC, string literals for xmlelement() are base64 encoded

    The only thing I can think of is that LibraryA/QRPGLESRC has CCSID 285, and LibraryB/QRPGLESRC has CCSID 65535. So I guess for string literals, the SQL functions use the CCSID of the source file?

    Comment

    sponsored links

    Collapse

    Working...
    X