Databases
StackOverflow2013
Postsdbo
POController logic for on-click events used with link_to
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POController logic for on-click events used with link_to
    primarykey
    data
    text
    <p>I am interested making a feature similar to that of SO's, where an user who has asked a question could select an answer from a list of responses, but am stuck on how to handle the click events from the controller perspective. </p> <p>Currently, I have the models <code>Question</code>, which <code>has_many</code> <code>answers</code>. Additionally, I have made an <code>Selection</code> model, which is meant to symbolize the answer selection, where each <code>Question</code> only could <code>has_one</code> selected answer. </p> <p>I render each questions's answers along with the question in the question's <code>show</code> action. In my <code>_answer</code> partial, I want to place the following logic: "if the user who has asked the question is logged on, he could see links to 'unselect' the answer <em>if</em> the related <code>selection</code> has that answer's <code>answer_id</code> already stored (in other words, marking that this answer was previously selected), pr otherwise he could 'select' the answer which stores the answer's <code>answer_id</code> in <code>selection</code>. (I should mention that I adapted most of the code below from <a href="https://github.com/schneems/reddit_on_rails/blob/master/part_two_comments_and_votes.md" rel="nofollow">Rails tutorial</a> here, where I (unfortunately) don't quite have a solid understanding how to use <code>POST</code> to match or assign attributes to an instance variable )</p> <pre><code> &lt;% if current_user?(answer.question.user) %&gt; &lt;% if current_user.selections.where(:answer_id =&gt; answer.id) == answer.id %&gt; &lt;%= link_to "unselect", selections_path(:selection =&gt; {:answer_id =&gt; nil}), :method =&gt; :post %&gt; &lt;% else %&gt; &lt;%= link_to "select", selections_path(:selection =&gt; {:answer_id =&gt; answer.id}), :method =&gt; :post %&gt; &lt;% end %&gt; &lt;% end %&gt; </code></pre> <p>My roadblock is in the controller, where I'm stuck on how to use <code>the create</code> method to assign the <code>@selection</code> variable to a new <code>answer_id</code> if the user selects a new answer via the "select" link. Any help, or any guides on how to write on-click events would be much appreciated. Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdaspianist
    1. USdaspianist
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POController logic for on-click events used with link_to
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POController logic for on-click events used with link_to
      1. USdaspianist
      1. VTFavorite
    1. COi don't understand what you want to achieve. Is it the onClick ajax call that is a problem, or the controller-side logic ? Also, sorry to ask this, but just to be sure - are you aware that client-side and server-side are totally decoupled, and that any interaction between the two requires a new request ?
      singulars
      1. POController logic for on-click events used with link_to
      1. USm_x
    2. COYes - at the present I am writing them as new request rather than Ajax (i.e. the "viewcount" for a page would go up if the user selects an answer). My question relates to the controller-side logic, and specifically what I should write in my `create` action. I hope this help clarifies things.
      singulars
      1. POController logic for on-click events used with link_to
      1. USdaspianist
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload