Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. PORuby nested modules as namespaces
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USSteve Benner
    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. VTDownMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI would suggest rethinking Ruby if it cannot natively support common OOP design strategies supported in other languages instead of burying your heads in the sand and blaming me for not doing what's possible in Ruby & following The Ruby Way(TM). Or calling modules "namespaces" which they apparently aren't. And please don't suggest I'm a noob, since I have a *lot* of experience in OO design from other languages, and I'm not a noob in Ruby either.
      singulars
      1. PO
      1. USSasQ
    2. CORuby is not designed like other languages, it is designed to be flexible, with a fundamental philosophy of 'there is more than one way to do it'. No one is suggesting you are a 'noob', but you are obvoiusly unaware of some of the established principles of Ruby. The purpose of a module **is to be mixed in**, which is why I mentioned there is 'more out there' to look at, it's a complex topic. Look, within a minute I found a source that could perfectly apply to your use case: http://blog.rubybestpractices.com/posts/gregory/037-issue-8-uses-for-modules.html
      singulars
      1. PO
      1. USSteve Benner
    3. CO*"The purpose of a module is to be mixed in, which is why I mentioned there is 'more out there' to look at"* I know mixins very well, and I even mentioned it at the beginning of my original post that it's *not* what I need. I need just namespaces, and modules are advertised as being the right tool for that job. So why they aren't? They seem to just *pretend* to be namespaces, but they're no more namespaces than classes are, if one is not able to alias or default them (which was the original purpose of introducing namespaces in the first place).
      singulars
      1. PO
      1. USSasQ
 

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