How to handle duplicate IDs
See original GitHub issueCurrently db creation uses INSERT OR IGNORE
rather than just INSERT
. The side effect is that only the first instance of a unique ID is entered into the database and all other instances with the same ID are ignored.
Should duplicate IDs in a GFF file be considered an error?
Issue Analytics
- State:
- Created 11 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
ID attribute values must be unique | Axe Rules | Deque Systems
Rename any duplicate ID attributes values. Duplicate IDs are common validation errors that may break the accessibility of labels, e.g., form fields, ...
Read more >duplicate-id - Accessibility Insights
Duplicate id values are a common, easily fixed validation error that can cause both scripting (such as JavaScript) and assistive technologies to behave ......
Read more >Solved: How to remove duplicate IDs based on applying cond...
Solved: Hi Team, I have below sample table in which i want to remove duplicate ID values based on Status Column ( it...
Read more >Avoid Duplicate id Attributes when Reusing Form Components
When we reuse components that rely on HTML id attributes, we run the risk of rendering HTML that results in duplicate IDs in...
Read more >Why are duplicate ID values not allowed in HTML?
So if you use duplicate ids in your HTML many libraries will not work as expected. The most libraries will get the first...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
True, and since the exons and CDSs in GTFs don’t usually have unique IDs, there’s already a mechanism for creating them on the fly. So to the user it may be as simple as providing
create_db()
amerge_strategy=
kwarg, say one of'merge'
(acts like we’ve been talking about above),'create_unique'
(makes a new ID upon collision), or'error'
(raisesNonUniqueIDError
or something).closing since this has been implemented for a while