Different behavior of “each” method in development and production
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have table in my ERB-template. Like this:
<table>
<% @users.each do |user| %>
<tr>
<td><%= user.id %></td>
<td><%= user.name %></td>
</tr>
<% end %>
</table>
It works fine. Suppose I have 2 users.
Table will be like this:
1 | foo
2 | bar
But for example, I decide to edit user with id1.
In development it will be correct. Like this:
1 | oof
2 | bar
But in production it will be:
2 | bar
1 | oof
After editing user always jumps to the end of table.
I think it because I use SQLite in local but Heroku uses PostgreSQL.
I'm newbie, so I can be wrong.
 
My question is: how should I change my code to make the code work correctly everywhere?
ruby-on-rails postgresql sqlite
add a comment |
I have table in my ERB-template. Like this:
<table>
<% @users.each do |user| %>
<tr>
<td><%= user.id %></td>
<td><%= user.name %></td>
</tr>
<% end %>
</table>
It works fine. Suppose I have 2 users.
Table will be like this:
1 | foo
2 | bar
But for example, I decide to edit user with id1.
In development it will be correct. Like this:
1 | oof
2 | bar
But in production it will be:
2 | bar
1 | oof
After editing user always jumps to the end of table.
I think it because I use SQLite in local but Heroku uses PostgreSQL.
I'm newbie, so I can be wrong.
 
My question is: how should I change my code to make the code work correctly everywhere?
ruby-on-rails postgresql sqlite
add a comment |
I have table in my ERB-template. Like this:
<table>
<% @users.each do |user| %>
<tr>
<td><%= user.id %></td>
<td><%= user.name %></td>
</tr>
<% end %>
</table>
It works fine. Suppose I have 2 users.
Table will be like this:
1 | foo
2 | bar
But for example, I decide to edit user with id1.
In development it will be correct. Like this:
1 | oof
2 | bar
But in production it will be:
2 | bar
1 | oof
After editing user always jumps to the end of table.
I think it because I use SQLite in local but Heroku uses PostgreSQL.
I'm newbie, so I can be wrong.
 
My question is: how should I change my code to make the code work correctly everywhere?
ruby-on-rails postgresql sqlite
I have table in my ERB-template. Like this:
<table>
<% @users.each do |user| %>
<tr>
<td><%= user.id %></td>
<td><%= user.name %></td>
</tr>
<% end %>
</table>
It works fine. Suppose I have 2 users.
Table will be like this:
1 | foo
2 | bar
But for example, I decide to edit user with id1.
In development it will be correct. Like this:
1 | oof
2 | bar
But in production it will be:
2 | bar
1 | oof
After editing user always jumps to the end of table.
I think it because I use SQLite in local but Heroku uses PostgreSQL.
I'm newbie, so I can be wrong.
 
My question is: how should I change my code to make the code work correctly everywhere?
ruby-on-rails postgresql sqlite
ruby-on-rails postgresql sqlite
asked Nov 23 '18 at 23:36
mechnicovmechnicov
1,6881620
1,6881620
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Explicitly specify order in your controller. If the order is unspecified, PostgreSQL does not guarantee any order, so assume it will be randomized.
@users = User.order(:id)#.limit/pagination
I would also advise you to have the same databases in development and production, if you take some time to setup PostgreSQL locally, it will pay off.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53453902%2fdifferent-behavior-of-each-method-in-development-and-production%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Explicitly specify order in your controller. If the order is unspecified, PostgreSQL does not guarantee any order, so assume it will be randomized.
@users = User.order(:id)#.limit/pagination
I would also advise you to have the same databases in development and production, if you take some time to setup PostgreSQL locally, it will pay off.
add a comment |
Explicitly specify order in your controller. If the order is unspecified, PostgreSQL does not guarantee any order, so assume it will be randomized.
@users = User.order(:id)#.limit/pagination
I would also advise you to have the same databases in development and production, if you take some time to setup PostgreSQL locally, it will pay off.
add a comment |
Explicitly specify order in your controller. If the order is unspecified, PostgreSQL does not guarantee any order, so assume it will be randomized.
@users = User.order(:id)#.limit/pagination
I would also advise you to have the same databases in development and production, if you take some time to setup PostgreSQL locally, it will pay off.
Explicitly specify order in your controller. If the order is unspecified, PostgreSQL does not guarantee any order, so assume it will be randomized.
@users = User.order(:id)#.limit/pagination
I would also advise you to have the same databases in development and production, if you take some time to setup PostgreSQL locally, it will pay off.
answered Nov 23 '18 at 23:55
Marcin KołodziejMarcin Kołodziej
4,5101315
4,5101315
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53453902%2fdifferent-behavior-of-each-method-in-development-and-production%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown