#399 Bug in haploinsufficiency field

closed
Mark Gibson
6
2008-06-20
2008-06-05
Jolene
No

This has been occuring everytime I try to check off the haploinsufficiency field for any object and commit it. When I retrieve the object, I find that the check marks have been moved to the paternal effect fields instead (which gets messy pretty quickly).

This is true when modifying objects that are retrieved from postgres or from a tab delimited file. I'm attaching an example of such a tab delimited file.

Discussion

  • Jolene
    Jolene
    2008-06-05

     
    Attachments
  • Jolene
    Jolene
    2008-06-05

    • priority: 5 --> 6
     
  • Mark Gibson
    Mark Gibson
    2008-06-05

    Logged In: YES
    user_id=422804
    Originator: NO

    does this happen consistently
    just tried this and it worked ok
    ???

     
  • Jolene
    Jolene
    2008-06-11

    Logged In: YES
    user_id=2032724
    Originator: YES

    Hey Mark,
    I did an svn update to revision 1839 today and that seems to have taken care of the bug in the Haplo field. Now whenever I do a retrieve on objects where I've checked off the Haplo field, it looks fine (i.e. the 'checked' value stays in the 'Haplo' field and no longer moves to the 'paternal effect' field).

    Thanks!

     
  • Jolene
    Jolene
    2008-06-20

    • status: open --> closed