#905 Unique Index on parts table forces "partnumber" to be unique

1.4
closed-wont-fix
None
5
2014-01-20
2013-12-03
turtle
No

The parts table has a index of unique is's and partnumber does not need to be unique.
A serach index seems to create this problem.
To fix the problem:
DROP INDEX parts_partnumber_index_u ;
CREATE INDEX parts_partnumber_index_u ON parts (partnumber)
WHERE obsolete is false;

1 Attachments

Discussion

  • Chris Travers

    Chris Travers - 2014-01-15

    Could you bring up your use case for this on the -devel list? We added this in 1.3 because of certain common issues. It would seem in your case, it might be important to relax the uniqueness constraint a bit. The question is, is there a way to do this without going back to the previous problems.

     
  • Chris Travers

    Chris Travers - 2014-01-15

    (for example, the unique constraint might be relaxed to non-assemblies, or the like)

     
  • Chris Travers

    Chris Travers - 2014-01-20
    • status: open --> closed-wont-fix
    • assigned_to: John Locke
     
  • Chris Travers

    Chris Travers - 2014-01-20

    Closing as wont-fix pending further discussions on the list. I will however be adding hooks for schema changes before data load but these will be tracked under the ar invnumber ticket instead.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks