-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Table doesn't exist during db:migrate #72
Comments
I have made this change to my fork at: https://github.com/josephbridgwaterrowe/promiscuous/tree/tweaks These are the projects that I'm trying promiscuous in: https://github.com/westernmilling/chancellor (publisher) |
May I suggest that the check for the _v column should not be done here. But instead document the requirement that pub/sub'd models need this column and perhaps include a generator as well. |
Thanks @josephbridgwaterrowe. I'll take a look at this soon. |
@kareemk, would you be interested in consuming this change through a pull request? And if so, I would value some thoughts on how we could test this behavior. Thanks. |
@josephbridgwaterrowe @michaeldauria maintains promiscuous now, i'll let him comment on this. |
@kareemk Thank you. |
+1 having this problem as well and @josephbridgwaterrowe 's fix resolves it. @michaeldauria is this something you'd consider merging in? thank you |
@samsongz I have another branch on my own fork over here https://github.com/josephbridgwaterrowe/promiscuous/tree/active_record_migrations that moves these checks into a CLI process, it also includes a fix for some issues I was having with AR 4.2.3 savepoints. |
When using ActiveRecord and "resetting" the database with
bundle exec rake db:drop db:create db:migrate RAILS_ENV=test
I receive the following error:I believe that this occurs when
lib/promiscuous/publisher/model/active_record.rb
checks for the existence of the_v
column.This is my new
lib/promiscuous/publisher/model/active_record.rb
which allows my migrations:The text was updated successfully, but these errors were encountered: