Encapsulate Your Changes

DBScript Is Transactions Made Easy

Implementing a transaction should be easy and DBvolution has made it so

DBScript translates the database transaction concept into a single Java class implemented similar to a thread. You fill in the actions you want performed in the script() method and throw an exception if something went wrong. The easiest transaction control ever

And we expect you to sub-class DBScript so you can have as complicated an object as you like and it still works beautifully. public class ScriptThatAdds2Marques extends DBScript {

   @Override
   public DBActionList script(DBDatabase db) throws Exception {
   DBActionList actions = new DBActionList();
   Marque myTableRow = new Marque();
   DBTable<Marque> marques = DBTable.getInstance(db, myTableRow);
   myTableRow.getName().setValue("TOYOTA");
   actions.addAll(marques.insert(myTableRow));

   List<Marque> myTableRows = new ArrayList<Marque>();
   myTableRows.add(new Marque(3, "False", 1246974, "", 3, "UV", "TVR", "", "Y", new Date(), 4, null));

   actions.addAll(marques.insert(myTableRows));
   return actions;
   }
}


When the test() or implement() of the DBScript is called the script method is automatically wrapped in the appropriate transaction for your database. The sanctity of your data is guaranteed

Creating and using the DBScript is the easiest part:

Use implement() to commit your changes and test() to roll them back. Throwing an exception is also guaranteed to roll the changes back to. You even get guaranteed protection from actions that will auto-commit your changes.

When you want DB to be easier and faster...

Get DBvolution from GitHub or Maven