StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7937394
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-10-29T06:40:33.180
FavoriteCount
0
LastActivityDate
2011-10-29T06:40:33.180
LastEditDate
LastEditorUserId
0
OwnerUserId
20178
ParentId
7934728
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
There are several ways that <a href="http://gacelaphp.com/documentation/usage/relationships-advanced/" rel="nofollow">Gacela</a> can handle automatically fetching related information: 1) Inheritance relationship In an example like the following: <pre><code>CREATE TABLE wizards ( wizardId INT UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT, fname VARCHAR(255) NOT NULL, lname VARCHAR(255) NOT NULL, ROLE ENUM('teacher', 'student') NULL, addressId INT UNSIGNED NULL, CONSTRAINT fk_address_wizard FOREIGN KEY (addressId) REFERENCES addresses(addressId) ON DELETE SET NULL ) ENGINE = Innodb; CREATE TABLE students ( wizardId INT UNSIGNED NOT NULL PRIMARY KEY, houseId INT UNSIGNED NOT NULL, isDAMembmer BOOL NOT NULL DEFAULT 0, CONSTRAINT fk_wizard_student FOREIGN KEY (wizardId) REFERENCES wizards(wizardId) ON DELETE CASCADE, CONSTRAINT fk_house_students FOREIGN KEY (houseId) REFERENCES houses(houseId) ON DELETE RESTRICT ) ENGINE = Innodb; </code></pre> The <code>students</code> table has the same primary key as the <code>wizards</code> table and because of the foreign key relationship definition, Gacela will detect that <code>students</code> inherits all of the fields from <code>wizards</code>. 2) Dependent relationship This is probably closer to what you're looking for: <pre><code>CREATE TABLE addresses ( addressId INT UNSIGNED AUTO_INCREMENT PRIMARY KEY, locationName VARCHAR(255) NOT NULL ) ENGINE = Innodb; CREATE TABLE wizards ( wizardId INT UNSIGNED NOT NULL PRIMARY KEY AUTO_INCREMENT, fname VARCHAR(255) NOT NULL, lname VARCHAR(255) NOT NULL, ROLE ENUM('teacher', 'student') NULL, addressId INT UNSIGNED NULL, CONSTRAINT fk_address_wizard FOREIGN KEY (addressId) REFERENCES addresses(addressId) ON DELETE SET NULL ) ENGINE = Innodb; </code></pre> However, this example still differs slightly from your example because the addressId is in the <code>wizards</code> table thus creating a belongsTo relationship rather than a hasMany which is what your example reflects. There is a third option available in Gacela, however I would first suggest that you consider that while it is often preferable to fetch data eagerly, there are real performance implications in always fetching eagerly rather than lazy loading data. It is for this reason that Gacela (and basically every other Data Mapper or ORM) by default does not eagerly fetch data from hasMany relationships. That said, you could write something like the following: <pre><code>class Mapper extends \Gacela\Mapper { public function find($id) { $query = $this->_source()->query(); $query->from('persons', array('fullName')) ->join('phones', 'phones.person=persons.id', array('phonenumber'), 'left') ->where('persons.id = :id', array(':id' => $id); $data = $this->_source->query($query); return $this->_load($data); } } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPHP ORMs and optimized relationship queries
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USNoah Goodrich
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. This table or related slice is empty.
CommentsPostId
1. COThanks Noah. The last way is nice but need to know Gacela codes well that takes some time but may help me to develop it for my purposes.
 singulars
 PostPostId
 PO
 UserUserId
 USAHHP

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.