Re: DB_NestedSet _verifyUserValues issue ?
| From: | Arnaud Limbourg | Date: | Thu, 06 Nov 2003 15:40:27 +0000 |
| Subject: | Re: DB_NestedSet _verifyUserValues issue ? | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-23301@lists.php.net to get a copy of this message | ||
mm
Daniel Khan wrote:
Arnaud Limbourg wrote: [..]mm, that is weird then. Maybe i has the same name and internal id, in lowercase and that could be a reason why i thought it worked. But then i upgraded to 1.3 and modified some of the field names i think. Would that be an explanation ? Arnaud/Ex: table is STRID | etc | NAME i define the $params as array( 'NAME' => 'whateverid' ) $ns = factory($params); then i try $ns->createSubNode(1, array('whateverid' => 'namehere')) It worked before (with 1.2.4) iirc. With 1.3 the array has to be array('NAME' => 'namehere')No it should alway have worked like the last line. NAME is the column name given by the user. whateverid is the internal dentifier inside the class. So the class doesn't depend on the index but on the value. E.g. STRID=>id The class will internally always use 'id' and not STRID. STRID is only used for reading and writing from/to the DB. I am that sure that it always worked like this as I use the class for some projects and a bug in this part of the class would screw up everything here. But - never say never - maybe it's a very hidden bug.