DB_NestedSet db incompatibilities?

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 > Hi! > > Andy Crain wrote: > > I noticed your post below regarding DB_NestedSet. I didn't know this to > > be the case, and can't see how DB_NestedSet would not work with, say, > > Postgres. > > I tried running it with Postgres not long ago and found two > incompatibilities: > 1) Usage of "INSERT INTO tablename SET field1=value1" syntax. I believe > this to > be quite non-standard. > 2) Usage of IF(..., ..., ...) within queries. I think CASE is a standard > construct and it is supported by Postgres. > > > Would you mind at all telling me what the incompatibility is, > > as I'm in the process of incorporating DB_NestedSet into Demian Turner's > > Seagull project? Also, as this is off topic, I didn't post to the list, > > but let me know if you feel I should do that. > > I don't see how this can be off-topic if we are discussing the PEAR class. > So > 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. >