StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20091761
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-11-20T09:18:29.593
FavoriteCount
0
LastActivityDate
2013-11-20T09:18:29.593
LastEditDate
LastEditorUserId
0
OwnerUserId
417562
ParentId
20091412
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
OK, you're doing something really weird here. You're outputting content in two ways. First, you output content in the normal way using <code>echo</code>. Fair enough! Second, you output content using <code>fputcsv</code> where the file handler leads to <code>php://output</code>. Also fair enough! But you shouldn't do both and expect it to work seamlessly. You want a CSV file, so the best way is to output all your data using <code>fputcsv</code>. At the moment, some of your data is encapsulated as a CSV file, and some of it isn't. This leads to output that you don't really want. I think you want something like this: <pre><code>foreach ($row as $value) { $output = array( $dealer_code, $dealer_name, $bodyshop_id, $bodyshop_name, $address1, $address2, $address3, $address4, $address5, $postcode, $bo_tel, $bo_email, $bc_name. $equity_contract, $value ); fputcsv($outstream, $output, ',', '"'); } </code></pre> <code>fputcsv</code> expects the data to be an array, so that's what we give it. The separate array fields will be separate columns in the CSV output. We don't <code>echo</code> any data: we store it in an array and then supply it to <code>fputcsv</code>. The second mistake you made was to send <code>$row</code> rather than <code>$value</code> to <code>fputcsv</code>. This meant that you were sending all the postcodes as received from the database row. Finally, you don't need <code><pre></code>. On a separate note, you really should have a better database structure. If you had a table of postcodes and a separate table of bodyshops and a foreign key linking them, the code to retrieve data would be a lot simpler, as would searching and updating it in future.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPHP to CSV not outputting fields correctly
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USlonesomeday
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPHP to CSV not outputting fields correctly
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThat makes sense as to why my output was weird. Thank you!
 singulars
 PostPostId
 PO
 UserUserId
 USuser3009232

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.