DB Design for Event Dependencies
Sounds like a "many:many" relationship.

See my tips on writing an optimal many:many table.

I assume you have a PRIMARY KEY for the Event table; perhaps the event name?  It should be used in the many:many table.