While investigating possible reasons for #350 I was checking whether the DB schema was up-to-date and noticed that que keeps it on a table comment.
Unfortunately this comment doesn't end up in Rails' structure.sql so it isn't added to new systems (including development and test databases) that run rake db:structure:load to prepare the database.
At first glance, there seem to be two possible solutions: get Rails to dump comments (might have additional benefits because one could use them to document the schema) or introduce a separate version column or table for que (less dependencies and reliance on specific Rails behaviour).
While investigating possible reasons for #350 I was checking whether the DB schema was up-to-date and noticed that que keeps it on a table comment.
Unfortunately this comment doesn't end up in Rails'
structure.sqlso it isn't added to new systems (includingdevelopmentandtestdatabases) that runrake db:structure:loadto prepare the database.At first glance, there seem to be two possible solutions: get Rails to dump comments (might have additional benefits because one could use them to document the schema) or introduce a separate version column or table for que (less dependencies and reliance on specific Rails behaviour).