Matt S Trout ha scritto:
On Mon, Sep 10, 2007 at 09:06:07AM +0200, Marcello Romani wrote:
Matt S Trout ha scritto:
On Mon, Aug 27, 2007 at 05:10:23PM +0200, Marcello Romani wrote:
Hi,
I'm developing an app using cat and dbic, with postgresql 8.1.
I've got a table with a "unique" column.
Wh
On Mon, Sep 10, 2007 at 09:06:07AM +0200, Marcello Romani wrote:
> Matt S Trout ha scritto:
> >On Mon, Aug 27, 2007 at 05:10:23PM +0200, Marcello Romani wrote:
> >>Hi,
> >>I'm developing an app using cat and dbic, with postgresql 8.1.
> >>I've got a table with a "unique" column.
> >>
> >>When I
Matt S Trout ha scritto:
On Mon, Aug 27, 2007 at 05:10:23PM +0200, Marcello Romani wrote:
Hi,
I'm developing an app using cat and dbic, with postgresql 8.1.
I've got a table with a "unique" column.
When I try to insert a record that violates that constraint (the code is
executed via txn_do
On Mon, Aug 27, 2007 at 05:10:23PM +0200, Marcello Romani wrote:
> Hi,
> I'm developing an app using cat and dbic, with postgresql 8.1.
> I've got a table with a "unique" column.
>
> When I try to insert a record that violates that constraint (the code is
> executed via txn_do($coderef)), I o
Hi,
I'm developing an app using cat and dbic, with postgresql 8.1.
I've got a table with a "unique" column.
When I try to insert a record that violates that constraint (the code is
executed via txn_do($coderef)), I obviously get an exception from DBIC.
The problem is that if I run myapp_se
