[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Upgrade duplicate key "transactions_pkey" problem SL 2.6.5 -> Ledgersmb 1.1.12

Subject: Re: Upgrade duplicate key "transactions_pkey" problem SL 2.6.5 -> Ledgersmb 1.1.12
From: "Robert Fraser" <..hidden..>
Date: Sun, 17 Jun 2007 20:25:25 +1200

On 6/17/07, Armaghan Saqib <..hidden..> wrote:

This is really strange.

Is this SL bug or something to do with postgres config?

Anybody know?

regards

The id clashes exist in SQL Ledger - this particular database has been through a few Postgres and SQL Ledger upgrades over the years.

This sort of thing is one of our major reasons wanting to move off SQL-Ledger.

Cheers
Rob

References:
- Upgrade duplicate key "transactions_pkey" problem SL 2.6.5 -> Ledgersmb 1.1.12
  - From: Robert Fraser
- Re: Upgrade duplicate key "transactions_pkey" problem SL 2.6.5 -> Ledgersmb 1.1.12
  - From: Chris Travers
- Re: Upgrade duplicate key "transactions_pkey" problem SL 2.6.5 -> Ledgersmb 1.1.12
  - From: Robert Fraser
- Re: Upgrade duplicate key "transactions_pkey" problem SL 2.6.5 -> Ledgersmb 1.1.12
  - From: Robert Fraser
- Re: Upgrade duplicate key "transactions_pkey" problem SL 2.6.5 -> Ledgersmb 1.1.12
  - From: Armaghan Saqib

Prev by Date: Re: Upgrade duplicate key "transactions_pkey" problem SL 2.6.5 -> Ledgersmb 1.1.12
Next by Date: Re: Upgrade duplicate key "transactions_pkey" problem SL 2.6.5 -> Ledgersmb 1.1.12
Previous by thread: Re: Upgrade duplicate key "transactions_pkey" problem SL 2.6.5 -> Ledgersmb 1.1.12
Next by thread: Re: Upgrade duplicate key "transactions_pkey" problem SL 2.6.5 -> Ledgersmb 1.1.12
Index(es):
- Date
- Thread