StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8308165
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2011-11-29T09:05:52.247
FavoriteCount
0
LastActivityDate
2011-11-29T15:20:02.387
LastEditDate
2011-11-29T15:20:02.387
LastEditorUserId
188535
OwnerUserId
188535
ParentId
8307701
PostTypeId
2
Score
10
ViewCount
0
LastEditorDisplayName
text
Body
To extract an argument from an invocation of your method, you need to look at the functions documented in <a href="http://docs.python.org/c-api/arg.html#parsing-arguments-and-building-values" rel="noreferrer">Parsing arguments and building values</a>, such as <a href="http://docs.python.org/c-api/arg.html#PyArg_ParseTuple" rel="noreferrer"><code>PyArg_ParseTuple</code></a>. (That's for if you're only taking positional args! There are others for positional-and-keyword args, etc.) The object you get back from <code>PyArg_ParseTuple</code> doesn't have it's reference count increased. For simple C functions, you probably don't need to worry about this. If you're interacting with other Python/C functions, or if you're releasing the global interpreter lock (ie. allowing threading), you need to think very carefully about object ownership. <pre><code>static PyObject * _sayhello_obj(PyObject *self, PyObject *args) { PyObject *obj = NULL; // How can I fill obj? static char fmt_string = "O" // For "object" int parse_result = PyArg_ParseTuple(args, fmt_string, &obj); if(!parse_res) { // Don't worry about using PyErr_SetString, all the exception stuff should be // done in PyArg_ParseTuple() return NULL; } // Of course, at this point you need to do your own verification of whatever // constraints might be on your argument. </code></pre> For calling a method on an object, you need to use either <a href="http://docs.python.org/c-api/object.html#PyObject_CallMethod" rel="noreferrer"><code>PyObject_CallMethod</code></a> or <a href="http://docs.python.org/c-api/object.html#PyObject_CallMethodObjArgs" rel="noreferrer"><code>PyObject_CallMethodObjArgs</code></a>, depending on how you construct the argument list and method name. And see my comment in the code about object ownership! Quick digression just to make sure you're not setting yourself up for a fall later: If you really are just getting the string out to print it, you're better off just getting the object reference and passing it to <a href="http://docs.python.org/c-api/object.html?highlight=print#PyObject_Print" rel="noreferrer"><code>PyObject_Print</code></a>. Of course, maybe this is just for illustration, or you know better than I do what you want to do with the data ;) <pre><code> char s[1024]; // How can I fill s, from obj.getName() ? // Name of the method static char method_name = "getName"; // No arguments? Score! We just need NULL here char method_fmt_string = NULL; PyObject *objname = PyObject_CallMethod(obj, obj_method, method_fmt_string); // This is really important! What we have here now is a Python object with a newly // incremented reference count! This means you own it, and are responsible for // decrementing the ref count when you're done. See below. // If there's a failure, we'll get NULL if(objname == NULL) { // Again, this should just propagate the exception information return NULL; } </code></pre> Now there are a number of functions in the <a href="http://docs.python.org/c-api/string.html#string-bytes-objects" rel="noreferrer">String/Bytes Objects</a> section of the <a href="http://docs.python.org/c-api/concrete.html" rel="noreferrer">Concrete Objects Layer</a> docs; use whichever works best for you. But do not forget this bit: <pre><code> // Now that we're done with the object we obtained, decrement the reference count Py_XDECREF(objname); // You didn't mention whether you wanted to return a value from here, so let's just // return the "None" singleton. // Note: this macro includes the "return" statement! Py_RETURN_NONE; } </code></pre> Note the use of <a href="http://docs.python.org/c-api/none.html#the-none-object" rel="noreferrer"><code>Py_RETURN_NONE</code></a> there, and note that it's not <code>return Py_RETURN_NONE</code>! PS. The structure of this code is dictated to a great extent by personal style (eg. early returns, <code>static char</code> format strings inside the function, initialisation to <code>NULL</code>). Hopefully the important information is clear enough apart from stylistic conventions.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPassing an object to C module, in Python
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USdetly
UserOwnerUserId
1. USdetly
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPassing an object to C module, in Python
 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
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

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.