I understand why we would want these to be in relational forms but in this
situation it isn't practical for a number of reasons. Normally that would
be what I would do.
However in this case the nature of the application is such that doing this
would cause an enormous load on the system as we wo
I understand how these lists come into existence (trust me I have had to
deal with enough of them). However, it is standard practice when working
with _relational_ databases to split those lists of numbers into unique
record pairs in a separate table. Your original source data was not
relational,
I believe you could do:
SELECT *
FROM Table
WHERE FIND_IN_SET(number, comma_delimited_field)
but this will be /very/ slow. This query is forced to
examine each and every row to determine whether or not your
number is in the field.
The better solution is to break up that field, which is
generally
You probably shouldn't have setup your database structure like that.
You should always break out multiple values into a separate table, each
value being stored in one record, then "link" them through a common
record id. A one to many relation.
As far as the database is concerned, those aren't de
