Skip to content

Conversation

davejachimiak
Copy link
Contributor

Say a developer begins constructing class Foo < ActiveRecord::Base and class Bar < ActiveRecord::Base. When she creates a migration to create a table for Foo, does rake db:migrate, she'll get an error from Annotate via the ActiveRecord adapter explaining that the bars table doesn't exist. Regardless of whether this is a good development practice, the error message is an annoyance.

@mykecameron
Copy link

👍

@wm
Copy link

wm commented Apr 17, 2013

I support this 👍

This is especially important when you want to run rollbacks and migrates too.

@ghost ghost assigned ctran Aug 15, 2013
@ctran
Copy link
Owner

ctran commented Aug 15, 2013

Do you mind re-submit this against master so I don't have to resolve the conflict manually?
Thanks.

@davejachimiak
Copy link
Contributor Author

@ctran rebased. Thanks!

ctran added a commit that referenced this pull request Aug 18, 2013
…xists Attempt model annotation only if table exists
@ctran ctran merged commit f509941 into ctran:master Aug 18, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants