Error in self referencing (nest relations) and tableName.

Jay Klehr added a comment - 17/Jan/13 1:16 AM We've encountered this as well, tried a lot of different things in our models/schema to get around it, but nothing worked. Made a test case here: https://github.com/diablomedia/doctrine1/blob/master/tests/Ticket/DC356TestCase.php Modified the doctrine core as suggested by Danny, but this change causes other Doctrine test to fail (Particularly tests/TableTestCase.php).

Danny Kopping added a comment - 06/Mar/12 1:01 PM I've just tested this scenario in as many different possible combinations as I could think of (all tables uppercase/PascalCase, all tables lowercase, some Pascal, some lowercase) and just by removing the "strtolower" function, the issue seems to be resolved.

Danny Kopping added a comment - 06/Mar/12 8:39 AM As Klaas mentions, this function incorrectly assumes that all databases will be named using lowercase letters. The problem arises in the following line: $cache [$key] ['dqlAlias'] = $this->_tableAliases [strtolower(implode('__', $e))] ; If one removes the "strtolower" function call, it will work for tables named with uppercase letters, but this is obviously quite an inelegant solution. Could you suggest an alternative solution? I'll be happy to make the change, test it and issue a pull request in GitHub

Klaas van der Weij added a comment - 17/Feb/11 9:34 AM This aching issue - as I traced the cord back to the wall - appears to originate from the fact that I use UPPERCASES in the names of my databas tables. When I user all lowercases: no problem. Hence it worked on my WAMP server (Windows just lowercases it all). Even when I so much as start the entity-table which an UPPERCASE: bang! Fatal error. This is not logical and, I presume, is a definite bug. Please, oh please fix this ..

Klaas van der Weij added a comment - 15/Feb/11 8:15 AM Same story over here. Same error with the following non-equal nest relation: <?php class TXCRDataNodeCRDataNode extends Doctrine_Record { public function setTableDefinition() { $ this ->setTableName('x_CRDataNode_CRDataNode'); $ this ->hasColumn('childNodeID', 'integer', 4, array( 'type' => 'integer', 'length' => 4, 'fixed' => false , 'unsigned' => false , 'primary' => true , 'autoincrement' => false , )); $ this ->hasColumn('parentNodeID', 'integer', 4, array( 'type' => 'integer', 'length' => 4, 'fixed' => false , 'unsigned' => false , 'primary' => true , 'autoincrement' => false , )); } public function setUp() { parent::setUp(); $ this ->hasOne('TCRDataNode as child', array( 'local' => 'childNodeID', 'foreign' => 'dataNodeID')); $ this ->hasOne('TCRDataNode as parent', array( 'local' => 'parentNodeID', 'foreign' => 'dataNodeID')); } } class TCRDataNode extends Doctrine_Record { public function setTableDefinition() { $ this ->setTableName('CRDataNode'); $ this ->hasColumn('dataNodeID', 'integer', 4, array( 'type' => 'integer', 'length' => 4, 'fixed' => false , 'unsigned' => false , 'primary' => true , 'autoincrement' => false , )); $ this ->hasColumn('value', 'string', 255, array( 'type' => 'string', 'length' => 255, 'fixed' => false , 'unsigned' => false , 'primary' => false , 'notnull' => false , 'autoincrement' => false , )); } public function setUp() { $ this ->hasMany('TCRDataNode as childNodes', array( 'local' => 'parentNodeID', 'foreign' => 'childNodeID', 'refClass' => 'TXCRDataNodeCRDataNode')); $ this ->hasMany('TCRDataNode as parentNodes', array( 'local' => 'childNodeID', 'foreign' => 'parentNodeID', 'refClass' => 'TXCRDataNodeCRDataNode')); } } $dn = Doctrine_Core::getTable('TCRDataNode')->find(5300); ?> .. and then when I .. <?php $pn = $dn->parentNodes; ?> .. it goes like: Notice: Undefined index: crdatanode in /home/shared/library/doctrine_1.2.2/Doctrine/Hydrator/Graph.php on line 288 Notice: Undefined index: in /home/shared/library/doctrine_1.2.2/Doctrine/Hydrator/Graph.php on line 289 Fatal error: Call to a member function getFieldName() on a non-object in /home/shared/library/doctrine_1.2.2/Doctrine/Hydrator/Graph.php on line 290 Using Doctrine 1.2.2 It seemed like the same thing as presented in the documentation