The problem you point out is one of the reasons this isn't the best way to
organize your data. A better way would be to keep your events table:
events
event_id
event_name
event_description
but properly normalize the sequences table by putting one event per row like
this:
table sequenc
Hi,
I have the following problem:
I want to store a list of events e_1 to e_n in one table, and in a
second table I would like to
store sequences of these events so that later I can ask questions like:
In what sequence has event e_5 happened as the third event.
My more or less trivial solution wou
