StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17597044
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-07-11T15:08:15.467
FavoriteCount
0
LastActivityDate
2013-07-11T15:08:15.467
LastEditDate
LastEditorUserId
0
OwnerUserId
434223
ParentId
17579315
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
First of all: <blockquote> Let's say the products I am storing come from a supplier who provide me with a unique product id which I want to use for my primary key in the database. </blockquote> That is a SKU number. Keep your primary keys for the database's management. If there is an external identifier, store that separately. Then I would always reuse the form for both insert and update. This becomes quite trivial when your SKU is a different property than your primary key. An example in code, see this model: <pre><code><?php class Product { protected $id; protected $sku; protected $name; // getters & setters here } class Form extends \Zend\Form\Form { public function __construct() { $this->add(array( 'name' => 'sku', )); $this->add(array( 'name' => 'name', )); } } class Controller extends \Zend\Mvc\Controller\AbstractActionController { public function createAction() { $form = new Form; $product = new Product; $form->bind($product); if ($this->getRequest()->isPost()) { $data = $this->getRequest()->getPost(); $form->setData($data); if ($form->isValid()) { // get service to update $service->create($product); // redirect to view } } return new ViewModel(array( 'form' => $form, )); } public function updateAction() { $form = new Form; // Load product based on the ID $form->bind($product); if ($this->getRequest()->isPost()) { $data = $this->getRequest()->getPost(); $form->setData($data); if ($form->isValid()) { // get service to update $service->update($product); // redirect to view } } return new ViewModel(array( 'form' => $form, 'product' => $product, )); } } </code></pre> This means the model keeps always an ID "for itself" and the SKU can be updated anytime. The update uses the id from the request (e.g. you have an url <code>admin/product/edit/123</code>) and the SKU number is differently and can be updated. By this means, the form can be kept the same for both the update and the create methods. I usually use a service layer to persist the object, you should do it the way you prefer.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POZF2 forms - insert and update forms
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJurian Sluiman
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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. COThanks Jurian, and yes I agree, primary key should be kept for the database management. The only reason I was trying to use the SKU in this case is because my models (and there are thousands of them) are updated regularly from an XML feed. By having the SKU as a primary key, I could use MySql's 'ON DUPLICATE KEY UPDATE' feature to very quickly update the database from a feed of thousands of items where the SKU is the unique identifier. Without this, for every item I would first have to search the database to see if it exists and make a decision to update according to the result.
 singulars
 PostPostId
 PO
 UserUserId
 USfamilymangreg
2. COYou can use an `INSERT IGNORE` query or use an `INSERT [...] WHERE NOT EXISTS` otherwise. For the first one (all errors in the insert will be skipped, mind that!) you just have a unique constraint on the SKU and then insert all the data from your feed. Though, that is a different topic and not really related to above ZF2 problem. Search SO about this topic, there are plenty questions about it :)
 singulars
 PostPostId
 PO
 UserUserId
 USJurian Sluiman

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.