Is it possible to apply filters on a model inside a view in Ruby on Rails?
Is it possible to apply filters on a model inside a view's code:
I use axlsx to generate Excel and I tried something like this inside my myview.xlsx.axlsx
file:
fs = MyModel.where(:Column1 => v1, :Column2 => v2)
puts fs[0].Column1
I got an error
undefined method Column1 for nil:NilClass
I am pretty sure there's nothing wrong with my filter so I wonder is it legal to have such a filter inside a view (and if such filters should only be placed inside a controller instead)?
ruby-on-rails axlsx
add a comment |
Is it possible to apply filters on a model inside a view's code:
I use axlsx to generate Excel and I tried something like this inside my myview.xlsx.axlsx
file:
fs = MyModel.where(:Column1 => v1, :Column2 => v2)
puts fs[0].Column1
I got an error
undefined method Column1 for nil:NilClass
I am pretty sure there's nothing wrong with my filter so I wonder is it legal to have such a filter inside a view (and if such filters should only be placed inside a controller instead)?
ruby-on-rails axlsx
add a comment |
Is it possible to apply filters on a model inside a view's code:
I use axlsx to generate Excel and I tried something like this inside my myview.xlsx.axlsx
file:
fs = MyModel.where(:Column1 => v1, :Column2 => v2)
puts fs[0].Column1
I got an error
undefined method Column1 for nil:NilClass
I am pretty sure there's nothing wrong with my filter so I wonder is it legal to have such a filter inside a view (and if such filters should only be placed inside a controller instead)?
ruby-on-rails axlsx
Is it possible to apply filters on a model inside a view's code:
I use axlsx to generate Excel and I tried something like this inside my myview.xlsx.axlsx
file:
fs = MyModel.where(:Column1 => v1, :Column2 => v2)
puts fs[0].Column1
I got an error
undefined method Column1 for nil:NilClass
I am pretty sure there's nothing wrong with my filter so I wonder is it legal to have such a filter inside a view (and if such filters should only be placed inside a controller instead)?
ruby-on-rails axlsx
ruby-on-rails axlsx
edited 17 hours ago
ray
895113
895113
asked 17 hours ago
Biju
928
928
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
It's legal, yet not advisable to use queries in the view. It's better to move them to a controller and even better to wrap them in a method inside the model.
In your case it looks that the query returns an empty collection, and that's why fs[0]
is nil
and you cannot call a method on it.
add a comment |
You can have such code in views, although you should try to avoid having logic in the view and move it to the controller or a helper. The problem here is that the active record relation is empty:
fs = MyModel.where(:Column1 => v1, :Column2 => v2) #=> #<ActiveRecord::Relation >
fs[0] #=> nil
You can use try
to avoid that an exception is raised if the relation is empty and return nil
instead:
fs[0].try(:Column1) #=> nil
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%2f53942970%2fis-it-possible-to-apply-filters-on-a-model-inside-a-view-in-ruby-on-rails%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
It's legal, yet not advisable to use queries in the view. It's better to move them to a controller and even better to wrap them in a method inside the model.
In your case it looks that the query returns an empty collection, and that's why fs[0]
is nil
and you cannot call a method on it.
add a comment |
It's legal, yet not advisable to use queries in the view. It's better to move them to a controller and even better to wrap them in a method inside the model.
In your case it looks that the query returns an empty collection, and that's why fs[0]
is nil
and you cannot call a method on it.
add a comment |
It's legal, yet not advisable to use queries in the view. It's better to move them to a controller and even better to wrap them in a method inside the model.
In your case it looks that the query returns an empty collection, and that's why fs[0]
is nil
and you cannot call a method on it.
It's legal, yet not advisable to use queries in the view. It's better to move them to a controller and even better to wrap them in a method inside the model.
In your case it looks that the query returns an empty collection, and that's why fs[0]
is nil
and you cannot call a method on it.
answered 17 hours ago
mrzasa
8,307103878
8,307103878
add a comment |
add a comment |
You can have such code in views, although you should try to avoid having logic in the view and move it to the controller or a helper. The problem here is that the active record relation is empty:
fs = MyModel.where(:Column1 => v1, :Column2 => v2) #=> #<ActiveRecord::Relation >
fs[0] #=> nil
You can use try
to avoid that an exception is raised if the relation is empty and return nil
instead:
fs[0].try(:Column1) #=> nil
add a comment |
You can have such code in views, although you should try to avoid having logic in the view and move it to the controller or a helper. The problem here is that the active record relation is empty:
fs = MyModel.where(:Column1 => v1, :Column2 => v2) #=> #<ActiveRecord::Relation >
fs[0] #=> nil
You can use try
to avoid that an exception is raised if the relation is empty and return nil
instead:
fs[0].try(:Column1) #=> nil
add a comment |
You can have such code in views, although you should try to avoid having logic in the view and move it to the controller or a helper. The problem here is that the active record relation is empty:
fs = MyModel.where(:Column1 => v1, :Column2 => v2) #=> #<ActiveRecord::Relation >
fs[0] #=> nil
You can use try
to avoid that an exception is raised if the relation is empty and return nil
instead:
fs[0].try(:Column1) #=> nil
You can have such code in views, although you should try to avoid having logic in the view and move it to the controller or a helper. The problem here is that the active record relation is empty:
fs = MyModel.where(:Column1 => v1, :Column2 => v2) #=> #<ActiveRecord::Relation >
fs[0] #=> nil
You can use try
to avoid that an exception is raised if the relation is empty and return nil
instead:
fs[0].try(:Column1) #=> nil
edited 12 hours ago
answered 17 hours ago
Ana María Martínez Gómez
1,184521
1,184521
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53942970%2fis-it-possible-to-apply-filters-on-a-model-inside-a-view-in-ruby-on-rails%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