After some digging :) It looks like (At least trunk) passwords are already escaped. The only character which is completely invalid is NUL. I don't think anyone actually wants to fix that.
If NULs are guaranteed out, SQL92 defines proper value quoting as: s/'/''/sg; (paraphrased from about 3 pages of text in X3H2-92-154/DBL section 5.2) Is there any underlying reason for validchars that I'm missing here? On Fri, 2005-05-06 at 00:54 +0000, Aaron Stone wrote: > On Thu, May 5, 2005, Geo Carncross <[EMAIL PROTECTED]> > said: > > > As long as the password is _ALWAYS_ quoted correctly, I have no problem > > with it. > > > > Wanna check? :) > > For proper quoting? I'm way too lazy. The current code would require quite > a bit of work to check quoting. > > Aaron > -- Internet Connection High Quality Web Hosting http://www.internetconnection.net/
