Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have this problem too sometimes. It can even make me feel like I'm getting too clever for Ruby. I know that isn't the case. In reality, I think I'm just using the language in a non-ideal way.</p> <p>When I have a series of one line methods, which I find to be the ultimate conclusion to just about any object oriented refactor, I figure I have also locked in the design. This is probably a fine thing to do if the code has matured around the problem, but probably a bad thing to do prematurely. For that reason, I try to keep the methods a little more willy-nilly and with some meat on the bones.</p> <p>I also find, that when I have a series of one line methods, I'm probably getting closer to realizing one facet of the beauty of lisp. But Ruby simple doesn't seem like the right place to be doing that, I argue.</p> <p>So instead, I would prefer to be Ruby like. Well, what does that mean?</p> <p>I've seen a lot of people do this.</p> <pre><code>def is_pull_available?; false end </code></pre> <p>Knowing to leave off the second <code>;</code> is a sign of someone who is at least familiar with that aspect of the Ruby grammar.</p> <p>This is fast and easy to do, but still kinda yuk.</p> <p>So what's a Ruby programmar to do? One perhaps with a little extra free time? Well, maybe they can create a DSL. That's all they've really done so far anyway, might as well present it that much more elegantly.</p> <p>So perhaps we turn</p> <pre><code>def is_pull_available? false end </code></pre> <p>into </p> <pre><code>pull_available false </code></pre> <p>All you really need to do to make this happen is...</p> <pre><code>def self.pull_available(value) define_method(:is_pull_available?) { value } end </code></pre> <p>And either throw that in a base class or mix it in from a module.</p> <p>I think this is really a step you will want to reserve for when you really want to lock in the domain logic and accentuate it. The more you polish it up, the more you are going to feel poorly when it changes.</p> <p><a href="http://pragprog.com/book/ppmetr/metaprogramming-ruby" rel="nofollow">Metaprogramming in Ruby</a> is probably a great book to read if you are interested in this sorta stuff.</p>
    singulars
    1. This table or related slice is empty.
    1. POMore concise way to write a series of one-line methods in Ruby?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBlake Taylor
    1. USBlake Taylor
    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. 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. VTUpMod
    1. COThis is an incredibly specific metaprogramming method, the metaprogramming takes up more space than the method it replaces. Maybe if lots of classes have this specific method, but even then, you have an extra translation between looking at the class and knowing what methods to call. I think the original syntax is declarative enough. Maybe it doesn't bother me because the code bases I work on all day are dramatically larger than this, but I'd be perfectly happy with the original code (other than some naming issues)
      singulars
      1. PO
      1. USJoshua Cheek
    2. COPretty much agree. Which is why I suggest larger, more substantive methods. Methods can be declarative too! I think this is hard to understand in theory, but easier to understand in practice.
      singulars
      1. PO
      1. USBlake Taylor
 

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