This is the problem. We have interfaces for Job in SlmQueue. But the problem is that in fact, this is a "QueueJob" entity. The user never deal with this. It creates classes that extends from SlmQueue\Job\AbstractJob, and insert it into the queue.

Basically, the main point of adding this is because basz uses Doctrien migrations and hence, when he uses it, it drops the table and only re-create mapped entities (thus he loses the queue_default table). My problem is that this QueueJob entity, the user should NEVER interact with it. Neither get it from a repository, nor directly create it (he should use a Job, and add it to the queue).

The only point of this entity is just so that when using Doctrine migrations, the table is generated. That is therefore my question : does it look sane to you to create an entity just for generate it but never use it, or is it better to just keep a SQL file and ask people to create the table manually.