Menu

#83 Lingering NONGENRE logic in SQLparsing and TableInfoClass

v1.0 (example)
closed
None
5
2016-02-12
2015-02-14
Ahasuerus
No

There is lingering NONGENRE logic in SQLparsing and TableInfoClass. It should have been deleted when we added a separate non-genre field to the title table in 2014-12.

Discussion

  • Ahasuerus

    Ahasuerus - 2016-02-12
    • summary: Lingering NONGENRE logic in SQLparsing --> Lingering NONGENRE logic in SQLparsing and TableInfoClass
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1 @@
    -There is lingering NONGENRE logic in SQLparsing. It should have been deleted when we added a separate non-genre field to the title table in 2014-12.
    +There is lingering NONGENRE logic in SQLparsing and and TableInfoClass. It should have been deleted when we added a separate non-genre field to the title table in 2014-12.
    
    • assigned_to: Ahasuerus
     
  • Ahasuerus

    Ahasuerus - 2016-02-12

    Updated description.

     
  • Ahasuerus

    Ahasuerus - 2016-02-12
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1 @@
    -There is lingering NONGENRE logic in SQLparsing and and TableInfoClass. It should have been deleted when we added a separate non-genre field to the title table in 2014-12.
    +There is lingering NONGENRE logic in SQLparsing and TableInfoClass. It should have been deleted when we added a separate non-genre field to the title table in 2014-12.
    
    • status: open --> closed
     
  • Ahasuerus

    Ahasuerus - 2016-02-12

    Fixed in:

    common/SQLparsing.py 1.167
    edit/tableInfoClass.py 1.22
    

    Installed in r2016-014 on 2016-02-12. Closing.

     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB