Databases
StackOverflow2013
Postsdbo
POGrails transactions (not GORM based but using Groovy Sql)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGrails transactions (not GORM based but using Groovy Sql)
    primarykey
    data
    text
    <p>My Grails application is not using GORM but instead uses my own SQL and DML code to read and write the database (The database is a huge normalized legacy one and this was the only viable option).</p> <p>So, I use the Groovy Sql Class (<a href="http://groovy.codehaus.org/api/groovy/sql/Sql.html" rel="nofollow">http://groovy.codehaus.org/api/groovy/sql/Sql.html</a>) to do the job. The database calls are done in Services that are called in my Controllers.</p> <p>Furthermore, my datasource is declared via DBCP in Tomcat - so it is not declared in Datasource.groovy.</p> <p>My problem is that I need to write some transaction code, that means to open a transaction and commit after a series of successful DML calls or rollback the whole thing back in case of an error.</p> <p>I thought that it would be enough to use <a href="http://groovy.codehaus.org/api/groovy/sql/Sql.html#commit()" rel="nofollow">http://groovy.codehaus.org/api/groovy/sql/Sql.html#commit()</a> and <a href="http://groovy.codehaus.org/api/groovy/sql/Sql.html#rollback()" rel="nofollow">http://groovy.codehaus.org/api/groovy/sql/Sql.html#rollback()</a> respectively.</p> <p>But in these methods Javadocs, the Groovy Sql documentation clearly states </p> <blockquote> <p>If this SQL object was created from a DataSource then this method does nothing.</p> </blockquote> <p>So, I wonder: What is the suggested way to perform transactions in my context? Even disabling autocommit in Datasource declaration seems to be irrelevant since those two methods "...do nothing"</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UStmanolatos
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGrails transactions (not GORM based but using Groovy Sql)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGrails transactions (not GORM based but using Groovy Sql)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POGrails transactions (not GORM based but using Groovy Sql)
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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