> But, if it does need to be changed, it seems like a terrible idea to > allow it to be done via SQL. Otherwise, the user can break the driver > by using SQL to set the list to something that the driver's not > expecting, and there's nothing the driver can do to prevent it.
... unless there is something like a (perhaps more generally useful) BECAUSE I HAVE :cookie AND I SAY SO clause.[1]
Correct me if I'm wrong but I'm pretty sure nothing in the protocol currently would allow this
While I see the utility at least for connection pools this does seem to be scope creep at the moment