StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20862217
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-31T19:12:28.503
FavoriteCount
0
LastActivityDate
2013-12-31T19:12:28.503
LastEditDate
LastEditorUserId
0
OwnerUserId
1607442
ParentId
20844760
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Your code working as expected: <code>char* data</code> array contains file's data. What's going wrong here is that your <code>char* data</code> array is misinterpreted by your visualizers (whatever you use to visualize: debugger visualizer, <code>std::cout</code>, etc). They all try to print null-terminated (c-style) string, but it terminates instantly, as first char is 0. Raw arrays can also be visualized in debuggers as pointers: address and only first data member's value (because it cannot know where array ends). In C# situation is different as arrays are objects there, much like <code>std::vector</code>s, so their size is known. Offtopic (sorry for that): I would like to comment your second, native C++ <code>BasicReader::ReadData</code> method implementation, as it hurts my C++ feelings ;) You trying to write C code in C++11 style. "There is more than one way to skin a cat", but there are some advices: <ul> <li>don't use raw pointers (char*), use STL containers instead (<code>std::vector</code>, <code>std::string</code>)</li> <li>have you really good reason to use <code>std::unique_ptr<uint8_t[]> data</code> + <code>size_t dataSize</code> instad of <code>std::vector<uint8_t></code>?</li> <li>avoid using raw <code>operator new()</code>, use STL containers, <code>std::make_shared</code>, <code>std::make_unique</code> (if available)</li> <li><code>seekg()</code>+<code>tellg()</code> file size counting can report wrong size in case of big files</li> </ul> Doesn't this code looks a little cleaner and more safe: <pre><code>std::vector<uint8_t> ReadData(const std::string filename) { std::vector<uint8_t> data; std::ifstream fs; fs.open(filename, std::ifstream::in | std::ifstream::binary); if (fs.good()) { auto size = FileSize(filename); // TODO: check here if size is more than size_t data.resize(static_cast<size_t>(size)); fs.seekg(0, std::ios::beg); fs.read(reinterpret_cast<char*>(&data[0]), size); fs.close(); } return data; } </code></pre> And usage is even more cleaner: <pre><code>std::vector<uint8_t> vertexShaderData = ReadData("VertexShader.cso"); if(vertexShaderData.empty()) { /* handle it*/ } auto wannaKnowSize = vertexShaderData.size(); </code></pre> As a bonus, you got a nice-looking debugger visualization. And safe <code>FileSize()</code> implementation. You can use either boost::filesystem, of <code>std::tr2</code> if your STL had implemented it. <pre><code>#include <filesystem> namespace filesystem = std::tr2::sys; /* or namespace filesystem = boost::filesystem */ uintmax_t FileSize(std::string filename) { filesystem::path p(filename); if (filesystem::exists(p) && filesystem::is_regular_file(p)) return filesystem::file_size(p); return 0; } </code></pre> Hope it helps somehow.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POc++ reading (.cso) compiled shader object returning \0
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USIvan Aksamentov - Drop
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POc++ reading (.cso) compiled shader object returning \0
 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
 VTUpMod
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.