Please consider the sample class below (ignoring any irrelevant mistakes...
Im a novice).

class A {
 protected static final String psString = "INSERT INTO some_table
VALUES(?)";
 protected static java.sql.PreparedStatement ps = null;

 protected final String s;

 /** I know this bit is very ugly and am open to suggestions? **/
 public static init(java.sql.Connection con) throws java.sql.SQLException {
   if(A.ps == null)
     A.ps = con.prepareStatement(A.psString);
 }

 public A(String s) {
   this.s = s;
 }

 public java.sql.Statement getStatement() throws java.sql.SQLException {
   A.ps.setString(1, this.s);
   return A.ps;
 }
}

If I were to;

1. Create database connection con
2. Use con to init the A class
3. Create multiple threads which instantiate A and invoke getStatement() on
those instances, placing the resulting java.sql.Statements into a batch (we
synchronise the addBatch()s)
4. Execute the batch (from the main thread)

I am worrying that if getStatement() is invoked concurrently the
"A.ps.setString(1, this.s);" might interfere with each other. Do I need to
worry?

Also, an unrelated question - is it possible to roll back CREATE TABLE
statements? I havent been able to.

Thanks.