Ruby on Rails
Sunday, December 27, 2015
On Sunday, December 27, 2015 at 7:17:17 PM UTC+1, Hassan Schroeder wrote:
I am a beginner, have a only two months study experience, so I would not know how to do it, honestly. Sorry for that!
Basically, I would like to check whether my suspicion is correct or not, and in case it is correct find a solution: I would appreciate any hint on how to do it.
In case everything is fine, I would feel surely relieved, but I would like to know anyway the reason of this repetition, unless someone of you reassured me that it is a normal behaviour due to some reason, for instance because PostgreSQL queries produces double responses like those or else...
This happens at Heroku, while in my production environment, that uses sqlite3, same queries do not load User and select users twice. So there everything looks fine.
My suspicion is due to the fact that in a topic branch (that I reset and cleaned) in my production env I once did duplicate by mistake the User model and migrated the migration which then was aborted, because the users table already existed. It may be silly but I am afraid that I did something wrong and caused this issue.
I am aware that all this sounds messy!
--
I can't imagine that being a possibility, but what's stopping you from
looking for yourself?
And if you're concerned that an action is causing duplicate queries
to be run, why not look at the DB logs?
I am a beginner, have a only two months study experience, so I would not know how to do it, honestly. Sorry for that!
Basically, I would like to check whether my suspicion is correct or not, and in case it is correct find a solution: I would appreciate any hint on how to do it.
In case everything is fine, I would feel surely relieved, but I would like to know anyway the reason of this repetition, unless someone of you reassured me that it is a normal behaviour due to some reason, for instance because PostgreSQL queries produces double responses like those or else...
This happens at Heroku, while in my production environment, that uses sqlite3, same queries do not load User and select users twice. So there everything looks fine.
My suspicion is due to the fact that in a topic branch (that I reset and cleaned) in my production env I once did duplicate by mistake the User model and migrated the migration which then was aborted, because the users table already existed. It may be silly but I am afraid that I did something wrong and caused this issue.
I am aware that all this sounds messy!
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/279a824f-f9fd-45e1-b053-8dc7e4b8337f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment