Big lists in a relational DB
Once the table gets really big, you will find that looking up an item to find out what list it is in becomes painfully slow.

I discuss that, plus provide efficient code, in my blog on ip-ranges.  Your use case (non-overlapping ranges of items "owned" by various "lists") seems to be the same problem.