From: Stephen D. <sd...@gm...> - 2006-07-20 22:54:40
|
On 7/17/06, Mike <nee...@gm...> wrote: > On 7/17/06, Stephen Deasey <sd...@gm...> wrote: > > I have a new database module called nsdbi which presents an API > > inspired by the ACS db procs. It's all built right into the driver > > framework. > > > > The nsdb module doesn't know anything about bind variable. The > > nspostgres driver *emulates* bind variables. The ACS procs provide a > > unified interface over the custom postgres and oracle drivers. > > > > For nsdbi I added bind variable support to the driver interface and > > native postgres support to the nsdbipg driver. > > > > It isn't just bind variable though. There are a few things in nsdb, > > and some in the nsdb/acs combo that are less than ideal. And there's > > some opportunities for new stuff: prepared queres, caching, > > performance hacks etc. > > > > I'll try and upload this to naviserver cvs soon as the basics seem to > > be working. It's dependent on Tcl 8.5 dicts, but 8.5 seems to be > > taking forever to release so I'm going to remove that. Might as well > > get it out there in whatever state so folks can bash on it. > > Stephen, > Two things. First, I think that removing the dict stuff is a > mistake. Reverting any work that was progress is not a good idea. It's not a problem. I have it in CVS on my laptop. Needs to be done anyway -- I want to run it and not depend on unreleased Tcl 8.5. > Second, I would love to help at least test this module or further its > progress. However, I need for this to happen <now> - as in, at the > latest by tomorrow evening EDT I will need to have at least something > I can use to access the database from naviserver. \ Sorry, missed this. I'm syncing the laptop every few days... > Right now I am > looking at 4 choices: > > 1) drop nsdb from naviserver and use nstcl after cleaning up any > multi-thread issues > 2) import ad_proc and 00-database from OACS and hack them up until > they work. (unfortunately the combination of the two is not possible > - nstcl ad_proc does not support positional parameters without default > values after named parameters ith default values) > 3) dig into OSSWEB and import its notion of ad_proc and db_* > 4) nsdbi and friends > > Numbers 3 and 4 sound most appealing to me at this moment because > these are "most supported" by the naviserver "community" - getting > help with 00-database is unlikely to happen for something unrelated to > OACS and nstcl hasn't been touched in 2+ years. The downside to > Number 3 is that i need to import a bunch of things with OSSWEB that > are not related to the database, and I am hesitant about doing so. > Your thoughts, comments, and opinions are most welcome. > You're using Postgres, right? |