Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If all you're looking for is a <a href="http://lbrandy.com/blog/2009/05/the-75-answer/" rel="nofollow noreferrer">75% answer</a>: grails</p> <p>I've done significant development on both platforms, though my major rails experience ended about a year and a half ago (before rails 2.x was released).</p> <p>I've been heavily involved in grails development since grails 0.5.</p> <p>The answer really depends quite a bit more on the developers and infrastructure that will be available to work on the project. If you're looking to deploy to a standard java app container (like Tomcat), I think that Grails is the better choice. If you're looking to do something with mongrel/rack/pound/etc. Pick rails.</p> <p>If there are particular gems/jars that fit your business problem, that would obviously affect your decision.</p> <p>The choice of Grails for me isn't so much because I think that it's better at solving all kinds of problems, but more because I like the grails developer community better and <a href="https://stackoverflow.com/questions/288074/groovy-advantages-over-jython-or-jruby/289269#289269">I like the groovy language a little more</a>.</p> <p>I've also found grails to be an easier sell to the places I've worked at over ruby/rails. There are many more java shops around here and it's less of a leap for them to make that transition.</p> <p>This is a personal preference and I could easily see someone else going the other way.</p> <p>Rails has quite a few things going for it, and I think the test driven development story there is much better (though I'm <a href="http://naleid.com/blog/2009/04/14/grails-build-test-data-01-plugin-released/" rel="nofollow noreferrer">working on trying to fix that</a>).</p>
    singulars
    1. This table or related slice is empty.
    1. POIs developer productivity higher on Ruby on Rails or Grails?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USTed Naleid
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs developer productivity higher on Ruby on Rails or Grails?
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COStrangely, the "75% answer" article you linked says Rails.
      singulars
      1. PO
      1. USChuck
    2. COHeh, I knew that, that was part of the point :). Either of the frameworks is good enough that if you're looking for a single answer and don't have any other big driving factors to pick one over the other, you can be successful. For me, where I'm at, and with the community I work in. Grails is the right answer, for someone else in different circumstances, Rails would be correct.
      singulars
      1. PO
      1. USTed Naleid
    3. COso bottom line is you don't see a significant difference in the languages to merit one over the other. Given that our standard at work is based on the JVM, grails provides a clear path to support the JVM standard. However, doesn't JRuby do the same thing?
      singulars
      1. PO
      1. USCam Wolff
 

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