Harald Armin Massa wrote: > I skimmed them, and in my eyes these changes involve a bit too much > magic to > be helpfull in the full range of database accesses. > > "Since columns is a sequence, and sequences in SQL are always joined by > ,, " > That is clearly wrong. With the SQL engine I use (PostgreSQL); there is the > data type of "ARRAY", so sequences are stored as array. > > "SELECT name, address FROM %s WHERE id = %S" > > As much as I understand: Big S means escaping, small s means "do not > escape" > ? For me this bears to much risk for to less gain. Especially since dynamic > exchanges of the names of tables and columns in SQL-queries is a totally > different beast then changing parameters. "Different beast" as: > > "usually has to happen in two steps" > > is quite incorrect concerning the "ususally" in my experience. The dynamic > exchanging of tablenames within statements is the ABSOLUTE minority, 1 out > of 40 or less statements. Especially since queries querying only one table > are the absolute minority; and the dynamic exchange of 3 tables is > undebuggable :) > > So from my point -1
Same here. Note that we have already discussed deprecating the pyformat binding format due to the many problems with it, e.g. users often mistakenly applying Python string formatting to the statement string. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Aug 16 2006) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: _______________________________________________ DB-SIG maillist - DB-SIG@python.org http://mail.python.org/mailman/listinfo/db-sig
