-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joshua D. Drake wrote: >> The multiple insert stuff is not only non-standard, it also encourages >> the bad practice of using literal values directly in the SQL string >> versus prepared statements with place holders. It is bad practice >> because it introduces SQL injection risks since the responsibility of >> literal value escaping is with the application instead of the driver. > > It is also something that users are clammoring for (and my customers). To > the point that I have customers using unions to emulate the behavior. Why? > Because it is really, really fast.
When inserting multiple rows in the same INSERT statement, how do you tell which row fails on a constraint or datatype-mismatch violation? - -- Ron Johnson, Jr. Jefferson LA USA Is "common sense" really valid? For example, it is "common sense" to white-power racists that whites are superior to blacks, and that those with brown skins are mud people. However, that "common sense" is obviously wrong. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEtAkFS9HxQb37XmcRAvfaAJ4viPqLt8g1aHR6H9l7lEjM13EWcgCgulAx rPuCH7OSDeb7RuKBuywm5k4= =RRQx -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
