This is a discussion on Terminology for client interface within the MySQL Database forums, part of the Database Forums category; Hi, I am finding myself in writing a Objective-C interface for MySQL via the C API. Actually it works ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hi,
I am finding myself in writing a Objective-C interface for MySQL via the C API. Actually it works fine, but now I hit on the terminology issue. There are several information sets and dimensions in a result, and the MySQL documentation makes not everything clear to me. These are so far my assumtions for naming the different types of information: - A "result" is is the abstract container/accessor for the results of a query. - A "result set" is a ordered set of rows. It wraps the concrete information (e. g. the returned rows of a SELECT query), WITHOUT meta information. - A "row" is a ordered set of cells. - A "cell" is the unique point of intersection of a row and a field/ column and thus is a single information entity. - A "field" holds the meta information (gathered via mysql_fetch_field()) for what I usually would call "column". I am bothered by the name "field", because I expect it to be a single entity. Spontaneous, fields are the same as cells for me. What MySQL calls "field", I'd call column. How do you think about this? Are the naming rules specified above well- defined for you? Thank you very much Christoph Lauterbach |