Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From <em><a href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#base64Binary" rel="noreferrer">base64Binary (XML Schema Part 2: Datatypes 3.2.16)</a></em>:</p> <blockquote> <p>[Definition:] <strong>base64Binary</strong> represents Base64-encoded arbitrary binary data. The <a href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#dt-value-space" rel="noreferrer">value space</a> of <strong>base64Binary</strong> is the set of finite-length sequences of binary octets. For <strong><em>base64Binary</strong> data</em> the entire binary stream is encoded using the Base64 Content-Transfer-Encoding defined in <a href="http://tools.ietf.org/html/rfc2045#section-6.8" rel="noreferrer">Section 6.8 of [RFC 2045]</a>.</p> </blockquote> <p>You then comment:</p> <blockquote> <p>When a WSDL has xsd:base64binary am I supposed to get a base64 response or a binary response or a base64 encoded string?</p> </blockquote> <p>You are supposed to get a base64 encoded string. That base64 encoded string <em>represents</em> the binary data. If you know the XML specification, this might be more obvious because you can not pass binary information with XML, you can only pass information that fit's into XML's character-range. And that range excludes characters that are part of binary data, especially control characters and the higher pane if you divide the binary octet into a lower and higher one. See <a href="http://www.w3.org/TR/REC-xml/#charsets" rel="noreferrer">Characters (Extensible Markup Language (XML) 1.0 (Fifth Edition) 2.2)</a> which shows that XML is about characters, not binary data. And which also shows which binary data those characters do form (and which they can not form).</p> <p>Therefore the <em>base64Binary</em> encoding has been defined as one way to transport binary data within an XML document. So what you've got inside the raw XML response to your SOAP request <em>is never binary</em> but base64 encoded binary data.</p> <p>Take care that your SOAP-client <em>might</em> already deal with this encoding and provide the data decoded.</p>
    singulars
    1. This table or related slice is empty.
    1. POSoap - base64binary data in PHP
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UShakre
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSoap - base64binary data in PHP
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe output was already decoded automatically by the SoapClient as you suggested. Didn't solve my problem yet but definitely answered my question. Thanks
      singulars
      1. PO
      1. USgalchen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload