On Dec 30, 2011, at 7:33 AM, Jeremy Chatfield wrote: > Hi - I'm using hobo 1.3 on rails 3.0.11 with ruby 1.9.2p290 > > I've tried to add "delayed_job". I set it up using "hobo g model delayed_job > queue:string ...". > > However, delayed_job has things it wants to do... I ran its' own processes to > set up delayed_job. I suspect that this has written something or overwritten > something that hobo depends on. The symptoms? > > Now, whenever I run "hobo g migration", I get a migration that wants to set > up the delayed_job table, again. I can do this time after time... a whole > series of migrations that want to set up the same table. And which cause > "bundle exec rake db:migrate" to fail, because the table is already defined. > I've tried removing the table definition manually from earlier migrations. > I've tried removing the table definition from all but the last migration, and > all but the penultimate migration. Nothing seems to stop hobo's desire to set > up the table, again. > > How do I stop hobo from trying to make a table that is already defined? There > is probably some file I need to make or edit with some magic in it... and I > can't work out what it is!
I suspect this is a mis-handled corner case - delayed_job's model is actually Delayed::Job, so maybe the migration generator isn't figuring things out correctly. Will take a look at it. --Matt Jones -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
