Expiration Manager And Related Job Tables?

[SoftwareGuyRob]

The ExpirationManager loops through through counter/job/list/set/hash table and performs a delete based on the expireAt timestamp. It loops/batches but essentially it's just

 DELETE FROM ""{_storage.Options.SchemaName}"".""{table}"" 
  WHERE ""id"" IN (
    SELECT ""id"" 
    FROM ""{_storage.Options.SchemaName}"".""{table}"" 
    WHERE ""expireat"" < NOW() 
    LIMIT {_storage.Options.DeleteExpiredBatchSize.ToString(CultureInfo.InvariantCulture)}

This works as expected for those tables; but I'm not seeing any mechanism to remove related data from the other tables. If a job is expired at gets deleted but the state information about that job remains in the state table along with parameter information in the jobparameter table.

This is 'as designed' right? I should be cleaning up these tables whenever I decide the information isn't relevant to me anymore?

EDIT: I do see the mechanism for removing data from these related tables. It's in the Install script; the foreign key is created with ON DELETE CASCADE. I don't know how or why, but seems likely a local one. My tables are missing that constraint even though the code.