On 2008.04.17, Andrew Piskorski <[EMAIL PROTECTED]> wrote: > > to "know" this)--so, caching/reuse of prepared statements really should > > be left up to the application code, as the developer ought to know when > > it can be reused vs. when it should be flushed/re-prepared. > > Yuck. IMO, the application developer MIGHT on occasion want that > level of control available, but forcing him to use it for every single > database access is sub-standard API design.
I never suggested that prepared statements _replace_ the current nsdb, but add to it. You would still be able to use ns_db (select, exec, etc.) if you don't want and/or need prepared statements for a query. Of course, given the elimination of SQL injection protection, it would be better to use prepared statements regardless, but, if folks are concerned with having a choice, they will still have a choice. -- Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- 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.
