-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/25/07 13:09, Andrew Sullivan wrote:
> On Fri, May 25, 2007 at 12:59:25PM -0500, Ron Johnson wrote:
>> Except that seemingly "boutique" features can be road-blocks to
>> implementing projects, which means that you never hear from them.
>
> Yes. That's a risk that free software projects take, alas. If you
> can't force your users to tell you what they're doing, then you can't
> be sure you have the right picture of what they're doing.
>
>> 1. transaction failure on statement failure[0], and
>
> I personally regard that as a feature, not a bug, so I'd be opposed
> to changing it.
Why? Not failing the whole transaction lets me decide how to handle
that *one* statement error, without have to code for retrying the
whole transaction.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGVyo6S9HxQb37XmcRAoSBAJ97Q99SwXNfj6s33uQpwKDBUOtHhwCeMXKk
QAZ5Ti/1btcT/RaR9dLmjTI=
=pAKC
-----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
