Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There is an open ticket for this bug here: <a href="https://rails.lighthouseapp.com/projects/8994/tickets/188-single-table-inheritance-bug-only-in-production-environment" rel="nofollow noreferrer">https://rails.lighthouseapp.com/projects/8994/tickets/188-single-table-inheritance-bug-only-in-production-environment</a></p> <p>The solution is listed at the bottom of this ticket: <a href="https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2389-sti-changes-behavior-depending-on-environment" rel="nofollow noreferrer">https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2389-sti-changes-behavior-depending-on-environment</a></p> <p>To quote:</p> <blockquote> <p>You must explicitly name subclasses in the parent class</p> <p>class ProjectFeedEvent &lt; FeedEvent</p> <pre><code>def self.subclasses [ProjectAddedEvent] end </code></pre> <p>end</p> </blockquote> <p>Part of the reason this issue has been around for a while and has not received much attention is that STI is not commonly necessary in Rails. Most contributors to Rails have decided not to use it in their own projects and therefore do not put time into making sure that it is well supported. Here's a blurb that briefly explains why you should not use it and suggests an alternative: <a href="http://www.matthewpaulmoore.com/ruby-on-rails-code-quality-checklist#sti" rel="nofollow noreferrer">http://www.matthewpaulmoore.com/ruby-on-rails-code-quality-checklist#sti</a></p> <p>My own personal experiences using STI at my company was that is seemed very useful at first, but as time went on we determined that we simply didn't need it enough to warrant the complexity. Since then, our project has grown dramatically and we have not missed it at all.</p>
    singulars
    1. This table or related slice is empty.
    1. POActiveRecord running different queries in production?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGdeglin
    1. USGdeglin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POActiveRecord running different queries in production?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis works perfectly, thanks! I've been rethinking the use of STI as well, but in my case I think it works well (common data structure, but different business rules for subclasses).
      singulars
      1. PO
      1. USLuke
 

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