On Wednesday 16 April 2008 17:06, Andrew Piskorski wrote: > As a design principle, remember that ns_db itself never cares what is > in the query at all! ns_db doesn't even care whether the "query" is > SQL or something else, the query is just some opaque string which gets > passed allong to the proper database driver. Therefore, the right > default approach for ns_db bind variable support is to transparently > pass through whatever bind variable syntax and usage each database and > its driver natively supports and expects.
Well put. ns_db is the interface between the tcl layer and the driver. You can add stuff above and below ns_db. Actually, ns_db has a little too much API. ns_db exec can handle a lot of the specialized API, and allow tcl level error detection and recovery. > If you want to experiment with building something extra to support a > single style of alternative bind-variable-like syntax across multiple > datbasese, that's fine, but it should never be the default behavior of > ns_db. Right, ns_db is more generic that even SQL, so it is hard to do too much. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
