On 6/13/05, Bernd Eidenschink <[EMAIL PROTECTED]> wrote: > > How about nsdb? This is an important module for people, but I'm > > hoping my newer nsdbi will be a big enough improvement that it becomes > > the new standard. In that case, it's kind of confusing to ship the > > old version. Maybe it's something for the future. What do folks > > think? > > In what ways will it be different (i'm curious :-)) ? > > If the existing drivers (and api) still work with nsdbi, I would vote for > using it and moving nsdb to the modules. So people can still use nsdb if they > need to. > > As with nscgi I would vote for leaving it as some useful software still needs > CGI.
Yes, I mean move nsdb into modules, not remove it entirely :-) I'll be using it myself for some time on old ACS sites that depend on it. The nsdbi driver interface is not compatible with nsdb. New hooks are needed to support native bind variables and prepared queries etc., and I took the oppertunity to (hopefully) simplify it. The postgres driver is only ~600 lines (with comments), so it shouldn't be too hard to port any of the old drivers. I still need to port a couple of patches to the server that nsdbi depends on, and then I'll import it into modules and you can try it out.
