StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4101832
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-11-04T22:04:38.883
FavoriteCount
0
LastActivityDate
2010-11-04T22:16:26.650
LastEditDate
2010-11-04T22:16:26.650
LastEditorUserId
45531
OwnerUserId
45531
ParentId
4101559
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
To update a row, you don't use: <pre><code>$myRow->update($data, $where); </code></pre> You use: <pre><code>$myRow->save(); </code></pre> But trying to use <code>update()</code> on a row object should throw an exception. So I'm guessing you're actually calling the <code>update()</code> function on the table object, and not the row object. <pre><code>$songs = new Songs(); //... $songs->update($data, $where); </code></pre> At that point the row object is never even used, the query is simply generated from the <code>$data</code> array and the <code>$where</code> clause. If you want to use the custom <code>_update()</code> method you would need to do something like: <pre><code>$songs = new Songs(); $song = $songs->find($id) //change some data $song->save(); </code></pre> Of course is also perfectly valid to add custom logic at the table level, and should be noted while calling an update or insert from the table object does not use the row object, calling <code>save()</code> on the row object proxies the table object. For example, from the <code>Zend_Db_Table_Row</code> <code>_doInsert()</code> function: <pre><code>$this->_insert(); //... $primaryKey = $this->_getTable()->insert($data); </code></pre> So if you have custom logic that you want to use every time you update a row (whether you update from the table object or the row object), it should be put into the table object. From the <a href="http://framework.zend.com/manual/en/zend.db.table.row.html" rel="nofollow">Zend_Db_Table_Row docs</a>: <blockquote> If you need to do custom logic in a specific table, and the custom logic must occur for every operation on that table, it may make more sense to implement your custom code in the insert(), update() and delete() methods of your Table class. However, sometimes it may be necessary to do custom logic in the Row class. </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCustom logic for updating a row
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USTim Lytle
UserOwnerUserId
1. USTim Lytle
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCustom logic for updating a row
 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
 VTAcceptedByOriginator
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.