That will do it. :)
The major difference between getParentRow and getDependentRowset() is
that getParentRow() will return a single row whereas
getDependentRowset() will return a rowset of (in your use case), a
single row. But both will work.
-ralph
Joseph Crawford wrote:
Please dis-reguard this question, i am just an idiot and had the table
name incorrect in my AUX model class.
Thanks,
Joseph Crawford
On Jul 6, 2009, at 1:38 PM, Joseph Crawford wrote:
I did some debugging by also adding the echo $select->__toString() in
the /Zend/Db/Table/Row/Abstract.php on line 914 which is in the
findDependentRowset method.
It seems to be outputting the same exact sql query
SELECT `isp_partners`.* FROM `isp_partners`
So for some odd reason it is not getting the dependent
rowset rather doing the same query and I am not sure why :(
Thanks,
Joseph Crawford
On Jul 6, 2009, at 1:19 PM, Ralph Schindler wrote:
In situations where I have auxiliary and/or errata tables (basically
a 1-1 relationship), I would look into peering to those rows via the
findParentRow($parentTable) method rather than finding as a
DependentRowset.
http://framework.zend.com/manual/en/zend.db.table.relationships.html#zend.db.table.relationships.fetching.parent
It is modeled effectively the same way, but you are using a different
approach for finding the actual Row.
Let me know if that helps!
-ralph
Now I have it working for the websites and keywords but cannot get
the isp_partners_aux to work. The issue seems to be that when I do
the findDependantRowset it does not get any data from the
isp_partners_aux table, rather it only contains the data from the
isp_partners table. There is only 1 row in each table that will
match. The aux table is just an external table that holds data
about isp_partners such as the username, etc. Below is my
controller followed by my model classes and then the output.
