Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I discovered Grails about a year ago, and haven't looked back. It takes a lot of ideas from Ruby on Rails (original it was named Groovy on Rails), and has a rich ecosystems of plugins / extensions. Grails, and underlying Grails language (superset of Java) make it a joy to program - you can really focus on the essentials. Its GORM functionality (a layer on top of hibernate) is also very powerful, and in addition to the plugin system, is one of two huge reasons to check it out (you can use it in your java apps as well). </p> <p>With version 1.2 about to come out, I feel it's feature-rich and mature enough to be something that any developer should have in their toolbelt. </p> <p>As far as performance, it's definitely less than that of pure Java, but you have everything from spring / hibernate / J2EE available to you to optimize, and you can always drop into pure java for some critical pieces of code. There have been some recent experiments with allowing to run part of the Groovy code using static method resolution, which, coupled with invokedynamic support, should provide huge performance boosts. </p> <p>Other ones to check out in Java are Spring Roo, and AribaWeb. </p> <p><strong>Update Based on Additional Qualifications</strong></p> <blockquote> <p>Scalability, Productivity, Documentation, and decent Resources consumption</p> </blockquote> <ul> <li>Scalability - you get the proven Java / Spring / Hibernate stack, though I can't say Grails provides much itself. </li> <li>Productivity - this is the main reason to use Grails. You do have a performance overhead, but Grails is what you use when development time / productivity is more important.</li> <li>Documentation - the grails docs are great, and there are at least three good books written on Grails alone. The community is thriving and very helpful. </li> <li>Resources Consumption - that is the one tradeoff. Grails (partially because of the underlying java stack) is resource-intensive. If I was building something like Google, Grails would not be the choice. However, in any web app of any sophistication, you'd do well for a caching solution, so same applies here. </li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POJava web frameworks
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJean Barmash
    1. USJean Barmash
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJava web frameworks
      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. COWell yeah, grail seems great. But think I'm going to try "Play", it looks really attractive.. the only thing I'm worried about is Resources Consumption and whether is worse or better than php/python/ruby, I didn't manage to find much about it on google.
      singulars
      1. PO
      1. USRoch
    2. COSounds good - play looks cool. Also check out AribaWeb videos - looks very sweet. Just keep in mind that with Grails, you also get the power of Groovy, which in itself is an advantage (though of course performance is a tradeoff).
      singulars
      1. PO
      1. USJean Barmash
    3. COOk, I'll have a look at AribaWeb. Play framework uses Groovy too for its templates ;-)
      singulars
      1. PO
      1. USRoch
 

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