I would guess that is so you can obsolete a part/service/what ever, and create a newer version which replaces the old one, without screwing up existing invoices posted with the old info.
Not, I suspect, the best way of handling this (invoices should not be an entity with variable items after their posted), but I believe that's why you can't make the partnumber unique. Luke On Sun, 15 Jun 2008, woodvorg wrote: > > Why is there no unique constraint on the partnumber field of parts? To me it > doesn't seem right; a part number should be a unique identifier for each > part. > > Easy fix, I just altered the parts table with a unique constraint, but this > produces nasty looking errors if you try to create a duplicate part. > -- "Fiat money and sustainable society are not compatible." - Peter Cajander ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Ledger-smb-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
