On Wed, Dec 09, 2009 at 03:15:23PM +0000, beamends wrote: > On Wed, 2009-12-09 at 22:30 +0800, David Godfrey wrote: > > Rich Shepard wrote: > > > On Wed, 9 Dec 2009, beamends wrote: > > > > "DBD::Pg::st execute failed: ERROR: duplicate key violates unique > > > > constraint "partsvendor_pkey" at LedgerSMB/IC.pm line 529. > > > > > > > > Error! > > > > > > > > INSERT INTO partsvendor > > > > (vendor_id, parts_id, > > > > partnumber, lastcost, > > > > leadtime, curr) > > > > VALUES (?, ?, ?, ?, ?, ?) > > > > ERROR: duplicate key violates unique constraint "partsvendor_pkey" > > > > "
Just to stick in my $0.02: I have had this type of semi-random "collision" problem (MS-SQL, however) due to hashed indices when the hashed values collide. Not sure if it would help here, but you might be a little careful about replacing stuff if they are using this sort of index - a little double-check in SQL code might be in order.. -- David \ Richardson \ Imagine whirled peas..... [email protected] \ The above is my own opinion - nobody else wants it! ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Ledger-smb-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
