LOVD 2.0

Welcome to the LOVD 2.0 bug tracking system. Please note that this bug tracking system is not for LOVD 3.0!

If you have any issues, please read the documentation and Frequently Asked Questions.
Please note that you need to register before you can submit bugs or feature requests.

Information By default, all closed tasks are hidden from view.
Click here to see all tasks.

Tasklist

FS#26 - Cannot use DBID out of sequence

Attached to Project: LOVD 2.0
Opened by Raymond Dalgleish (rwmd) - Friday, 02 May 2008, 17:17 GMT+2
Last edited by Ivo F.A.C. Fokkema (ifokkema) - Monday, 19 May 2008, 14:45 GMT+2
Task Type Feature Request
Category Modules → ShowMaxDBID
Status Closed
Assigned To Ivo F.A.C. Fokkema (ifokkema)
Operating System All
Severity Low
Priority Normal
Reported Version 2.0-06
Due in Version 2.0-07
Due Date 2008-05-30
Percent Complete 100%
Votes 0
Private No

Details

Prior to the update of ShowMaxDBID in Version 2.0 Build 06, I had inadvertently assigned multiple different DBID values to the same variant on a small number of occasions. When I realised this, I manually corrected these inconsistencies and that left me with 10 DBID values that were no longer in use and each of which was a samller value than the current maximum value.

Since the update to Version 2.0 Build 06, I can no longer use these \"spare\" DBID values and LOVD generates an error message. The \"problem\" is that the new version of ShowMaxDBID is not testing to see if the value entered by the user is already in use or not. It\'s simply testing to see if the entered value is greater than the current maximum value.

It\'s a minor point, but it would be nice for the sake of consistency to have no gaps in the sequence of DBIDs used for any given gene.
Closed by  Ivo F.A.C. Fokkema (ifokkema)
Friday, 30 May 2008, 13:57 GMT+2
Reason for closing:  Fixed
Comment by Ivo F.A.C. Fokkema (ifokkema) - Monday, 05 May 2008, 17:25 GMT+2
You\'re right, you should not be forced to use the next available ID (which is the current situation) but also allowed to use a spare empty one. After a quick look at the code I believe this should not be hard to implement.

Loading...