Re: upgrades and database integrity.

[Michael Richardson <..hidden..>]

>>>>> "Alvin" == Alvin Starr <..hidden..> writes:
    Alvin> I started using sql-ledger about 5 years ago and my last
    Alvin> upgrade was 2.6.19 This was partly due to the fact that I was
    Alvin> going to move to ledger-smb one of these days.  Well the day
    Alvin> came and I upgraded through to ledgersmb 1.2.18.  Everything
    Alvin> seemed ok till we started getting the following errors while
    Alvin> posting a payment to an invoice.

    Alvin> ==================== *DBD::Pg::st execute failed: ERROR:
    Alvin> duplicate key violates unique constraint "transactions_pkey"
    Alvin> at LedgerSMB/IS.pm line 862. * Error!  *INSERT INTO ar (id,
    Alvin> customer_id) VALUES (?, ?)  ERROR: duplicate key violates
    Alvin> unique constraint "transactions_pkey"* ====================

    Alvin> This error seems to delete the invoice from the AR.

    Alvin> A little googling and I found some comments about this being
    Alvin> a referential integrity problem.  The question is how do I
    Alvin> fix it?

I do not know how to fix the root cause. I do not know why, or when it happens.
It happens when I post an existing transaction, sometimes.

Go Back to the form, and click on "post as new", and you'll get it all
back....

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] ..hidden.. http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition.