Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id DEEE3C24693 for ; Fri, 30 Dec 2011 07:07:34 -0400 (AST) Received: from meteor.mejor.pl ([2001:470:1f15:1b61::2]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RgaJB-0000OP-5d for pgsql-sql@postgresql.org; Fri, 30 Dec 2011 11:07:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mejor.pl; s=cokolwiek; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=5c1x2IG9o87NAoc1IECp0KlAIXHfstT6h4hLKt4IJMY=; b=UbUXuKa4UcaCBlgxhVtKafxV/GF8Jw/phhb04/2ohf9do7vMRfc2gRwJEuZd+lrtvDjxjzSUdgtatVtMXXb29YHMqrv+84mjfjIj5JQGv88rNxJhCYkLd1iFLFB3vvTl; Received: from cadera.waw.pl ([62.121.127.119] helo=[192.168.138.46]) by meteor.mejor.pl with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.77) (envelope-from ) id 1RgaIy-0003lU-7B for pgsql-sql@postgresql.org; Fri, 30 Dec 2011 12:07:20 +0100 Message-ID: <4EFD9B67.30308@mejor.pl> Date: Fri, 30 Dec 2011 12:07:19 +0100 From: =?UTF-8?B?TWFyY2luIE1pcm9zxYJhdw==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111214 Thunderbird/8.0 MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: Re: Re: Current transaction is aborted, commands ignored until end of transaction block References: <4EFD3D32.9060902@greenpeace.org> <13131805-BCBB-42DF-953B-27EE36AAF213@yahoo.com> <4EFD79BA.50508@greenpeace.org> <201112301044.33861.leif@solumslekt.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -3.3 (---) X-Archive-Number: 201112/94 X-Sequence-Number: 36155 W dniu 30.12.2011 12:03, Thomas Kellerer pisze: > Leif Biberg Kristensen wrote on 30.12.2011 10:44: >> Fredag 30. desember 2011 09.43.38 skrev Jan Bakuwel : >> >>> Would be nice to have an option in PostgreSQL something along the lines >>> of: 'abort-transaction-on-constraint-violation = false'.... >> >> That option is called MySQL with MyISAM tables. >> > Not true. > > Oracle and others (I believe at least DB2) behave such that you can > insert a bunch of rows and if one or more throw a constraint violation, > the transaction can still be committed persisting those that do not > violate the constraint. Hi, isn't this option: http://www.postgresql.org/docs/current/static/sql-set-constraints.html ? Regards