Re: DB_NestedSet db incompatibilities?
| From: | Daniel Khan | Date: | Wed, 05 Nov 2003 23:25:33 +0000 |
| Subject: | Re: DB_NestedSet db incompatibilities? | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-23263@lists.php.net to get a copy of this message | ||
Hello,
I am trying to catch up as didn't read much mail while beeing at the phpcon.
Unfortunately I can't find the first post by Alexey anywhere so a link to it would be helpful.
Andy Crain wrote:
Thanks very much, Alexey. Anyone else aware of this, or other dependencies in DB_NestedSet? The first one below (insert into table field1=value1), at least, seems like an easy fix. Andy [..]
Some time ago there was a posting on the list saying that someone did slightly modifications to run it on oracle. A patch was promised but never sent and I was too lazy to ask for it again :\ Alexey is right when saying that NestedSets can be done with SP on other RDBMS but in Andy's case (usage in an distributed project) the package should obviously work on Postgres,.. too. SQLite tests should also be done. So what I will do is to set this issues on top of my todo list and I will do my best to release a more cross DB compatible package (along with other fixes) soon. As I don't have access to all available RDBM's I would be happy if other people would also test and report problems. Thank's for the suggestions -- Daniel KhanSo feel free to forward this to the list. Besides, I'd advise against using DB_NestedSet with Postgres or other RDBMS except MySQL. The same functionality (except probably getting and processing the tree) can and should be implemented server-side in its procedural language. If you are interested, I can send you some examples in PL/PgSQL for this. Basically the class was indeed only developed and tested against mySQL.