• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Agile Database - Java JDBC concerns

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
When using Java to access database tables, one of the biggest concern is the transaction control (commit or rollback). Does anyone have any guideline or solution to address my concern.
Thanks, Joseph Yin
jyin@qualcomm.com
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Interesting. Do you have any specific concerns regarding how an agile database design would affect your transaction management?
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Commit if you want the changes to be persistent, rollback otherwise, so it seems to me. But I guess I don't understand the question...?
 
Ranch Hand
Posts: 341
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
By default in JDBC transaction starts and commits after each statement's execution on a connection. But it gives poor performance when multiple statements on a connection are to be executed.
 
Lasse Koskela
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by surasak lee:
By default in JDBC transaction starts and commits after each statement's execution on a connection. But it gives poor performance when multiple statements on a connection are to be executed.

But this still doesn't have anything to do with agile database design...
 
Ranch Hand
Posts: 166
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This topic seems appropriate for JDBC forum.
 
Ranch Hand
Posts: 173
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Given a java.sql.Connection instance conn, use

Now you can commit only when you want to.
Craig
[ January 14, 2004: Message edited by: Craig Demyanovich ]
[ January 14, 2004: Message edited by: Craig Demyanovich ]
 
Ranch Hand
Posts: 8945
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What is agile database? This is a new term .
 
Wanderer
Posts: 18671
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm moving this to the JDBC forum.
 
Lasse Koskela
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

What is agile database? This is a new term .

There is no such a thing. There's agile database design or development, however.
[ January 14, 2004: Message edited by: Lasse Koskela ]
 
author
Posts: 608
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
For Agile Database material, check out www.agiledata.org.
When it comes to transaction control and agile databases, my only advice is to understand transaction control, concurrency control, recognize you have options, and the pick the right approaches. http://www.agiledata.org/essays/concurrencyControl.html might help a bit.
- Scott
 
reply
    Bookmark Topic Watch Topic
  • New Topic