StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2829560
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-05-13T19:11:14.083
FavoriteCount
0
LastActivityDate
2010-05-13T19:11:14.083
LastEditDate
LastEditorUserId
0
OwnerUserId
249900
ParentId
2144399
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Well, Here's my suggestion. The issue is, you have to snag the right part of the result, one that is something you can actually iterator over. Unfortunately, all the inspecting in the world won't help you because it's a huge blob of unreadable text. What I do is this: <pre><code>File.open('myresult.yaml', 'w') {|f| f.write(result.to_yaml) } </code></pre> This will be a much more human readable format. What you are probably looking for is something like this: <pre><code> --- !ruby/object:SOAP::Mapping::Object __xmlattr: {} __xmlele: - - &id024 !ruby/object:XSD::QName name: ListAddressBooksResult <-- Hash name, so it's resul["ListAddressBooksResult"] namespace: http://apiconnector.com source: - !ruby/object:SOAP::Mapping::Object __xmlattr: {} __xmlele: - - &id023 !ruby/object:XSD::QName name: APIAddressBook <-- this bastard is enumerable :) YAY! so it's result["ListAddressBooksResult"]["APIAddressBook"].each namespace: http://apiconnector.com source: - - !ruby/object:SOAP::Mapping::Object </code></pre> The above is a result from DotMailer's API, which I spent the last hour trying to figure out how to enumerate over the results. The above is the technique I used to figure out what the heck is going on. I think it beats using REXML etc this way, I could do something like this: <pre><code>result['ListAddressBooksResult']['APIAddressBook'].each {|book| puts book["Name"]} </code></pre> Well, I hope this helps anyone else who is looking. /jason
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to parse SOAP response from ruby client?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJ. Martin
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.