StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8948625
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-01-20T22:22:18.620
FavoriteCount
0
LastActivityDate
2012-02-22T21:05:03.813
LastEditDate
2012-02-22T21:05:03.813
LastEditorUserId
970988
OwnerUserId
970988
ParentId
8899110
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
From the meta_search gem page you can see that for boolean values the 'Wheres' are: <ul> <li>is_true - Is true. Useful for a checkbox like “only show admin users”.</li> <li>is_false - The complement of is_true.</li> </ul> so what you need is to change the generate input name from 'completed_eq' to be 'completed_is_true' or 'completed_is_false'. The only way I have found this possible to do is with Javascript, since by looking at the Active Admin code, the 'Wheres' are hardcoded for each data type. I would usually have a line like this in my activeadmin.js file (using jQuery) <pre><code>$('#q_completed_eq').attr('name', 'q[completed_is_true]'); </code></pre> or <pre><code>$('#q_completed_eq').attr('name', 'q[completed_is_false]'); </code></pre> Terrible and ugly hack but have found no other solution myself. Be careful to enable this only in the pages you want. --- NEW FOR VERSION 0.4.2 and newer --- Now Active Admin uses separate modules for each :as => ... option in the filters. So for example you can place the code below inside an initializer file <pre><code>module ActiveAdmin module Inputs class FilterCustomBooleanInput < ::Formtastic::Inputs::SelectInput include FilterBase def input_name "#{@method}_is_true" end def input_options super.merge(:include_blank => I18n.t('active_admin.any')) end def method super.to_s.sub(/_id$/,'').to_sym end def extra_input_html_options {} end end end end </code></pre> and the use <pre><code>:as => :custom_boolean </code></pre> where you specify your filter.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POActiveAdmin, polymorphic associations, and custom filters
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USglampr
UserOwnerUserId
1. USglampr
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POActiveAdmin, polymorphic associations, and custom filters
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COThanks for answering! I'll have a look and see if this works for me. If it does, I'll mark this as the correct answer.
 singulars
 PostPostId
 PO
 UserUserId
 USjustinbach
2. COThanks! This works great for me!
 singulars
 PostPostId
 PO
 UserUserId
 USMelinda Weathers

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.