On Sun, Jul 31, 2011 at 9:17 PM, Lyle <[email protected]> wrote: > Hi, > We've been making plenty of mistakes and amending posted records > quite a lot. A few times now we've had a duplicate key error come up, > same error comes up if we go back and try posting again. Then after > going back to the main list and refreshing the record is lost. > I assume this is because something is getting out of sync in the DB, > I'll be looking through the data directly in the DB next week looking > for lost fragments and such. Before I do this, is this a known issue > with a fix? Is there a data integrity check script already available > that I don't know of? I will of course submit my findings here, but it's > only for the current stable release, not the dev version.
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. Best Wishes, Chris Travers > > > Lyle > > > ------------------------------------------------------------------------------ > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/ledger-smb-users > ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
