[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Changing tax.pm in 1.21 for a new tax which replaces two old taxes
- Subject: Re: Changing tax.pm in 1.21 for a new tax which replaces two old taxes
- From: Gerald Chudyk <..hidden..>
- Date: Mon, 5 Jul 2010 16:38:16 -0700
On Mon, Jul 5, 2010 at 10:51 AM, Chris Travers <..hidden..> wrote:
> Currently what I'm doing for my customers is to set the rate to 0
> effective when the tax is no longer collected, and to remove it from
> the drop down once no more invoices could be generated (usually at
> next book close).
>
I think this is the error code returned when I tried this earlier.
Apologies, but I'm still running my modified code. I will try this
from a clean codebase later:
DBD::Pg::st execute failed: ERROR: duplicate key violates unique
constraint "tax_pkey"
Error!
INSERT INTO tax (chart_id, rate, taxnumber, validto,
pass, taxmodule_id, validfrom)
VALUES (?, ?, ?, ?, ?, ?, ?)
ERROR: duplicate key violates unique constraint "tax_pkey"