On 01/08/2011 06:34, Chris Travers wrote:
On Sun, Jul 31, 2011 at 10:29 PM, Chris Travers<..hidden..> wrote:Reposting is not technically recommended or fully supported, However if you must, please apply sql/fixes/transactions_pkey_repost.sql to your database. It will prevent this problem.... It also occurs specifically when an invoice has been reposted twice.
I've had chance to look at this script. As I saw this error a few times, I assume I have rows in the transactions table that are missing a match in either ap or ar? ... hmmm... after taking a look, with: select t.id, ap.id, ar.id from transactions t left join ap on t.id=ap.id left join ar on t.id=ar.id;
Maybe the opposite is true?select t.id, ap.id, ar.id from transactions t left join ap on t.id=ap.id left join ar on t.id=ar.id where ap.id is not null or ar.id is not null;
id | id | id -------+----+------- 10697 | | 10697 10701 | | 10701 10725 | | 10725 10709 | | 107094 having gone wrong is probably about right, but now I'm a bit lost... Those seem to be from ar transactions that are showing up properly. Any pointers?
Lyle
Best Wishes, Chris Travers ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Ledger-smb-users mailing list ..hidden.. https://lists.sourceforge.net/lists/listinfo/ledger-smb-users