Mirage 1.1.3 is now available!

Mirage is a simple SQL centric database access library. See the following URL to know about Mirage:

• http://amateras.sourceforge.jp/site/mirage/welcome.html

New features in Mirage 1.1.3:

• Added SchemaUpdater and SchemaUpdateListener to update database schema automatically.
• Added Session#setRollbackOnly() and Session#isRollbackOnly() to rollback transaction without exception.
• SQL parsing result caching for performance improvement. You can control cache mode via SqlManagerImpl#setCacheMode().
• Oracle hint support in 2-way SQL
• Added ResultEntityCreator interface to extends SqlManager.
• Added PropertyExtractor interface to extends BeanDesc.
• Scala wrapper named mirage-scala is available.

This release contains the first release of mirage-scala. This is a wrapper of Mirage for Scala.

I have tested so many features and patterns in mirage-scala. However I couldn't believe how interface is best for mirage-scala. So I decided to release with minimum features in the first release. mirage-scala has not enough features now, however it will be expanded in the future.

I hope Mirage helps your development. Enjoy!

mirage-scala: Scala binding of Mirage

I started working for mirage-scala that is Scala binding of Mirage. mirage-scala works as wrapper of Mirage and provides the best interface to access to the database using Mirage for Scala.

This is a simple example to query using mirage-scala:

// A class that mapped to ResultList
class Book (
  val bookId: Int,
  val bookName: String,
  val author: String,
  val price: Int
)

// get Session and SqlManager
val session: Session = SessionFactory.getSession()
val sqlManager: SqlManager = session.getSqlManager()

// begin transaction
session.begin()

try {
  val books: List[Book] = sqlManager.getResultList(
    classOf[Book], Sql("""
      SELECT BOOK_ID, BOOK_NAME, AUTHOR, PRICE
      FROM BOOK
      /*IF author!=null*/
        WHERE AUTHOR = /*author*/
      /*END*/
    """), Map("author"->"Naoki Takezoe"))
  
  books.foreach { book =>
    println("bookId: " + book.bookId)
    println("bookName: " + book.bookName)
    println("author: " + book.author)
    println("price: " + book.price)
    println("--")
  }
  
  // commit transaction
  session.commit()
} catch {
  // rollback transaction
  ex: Exception => session.rollback()
}

A most important feature of Mirage is dynamic SQL template named 2waySQL. In Mirage, you have to create it as an external file on the classpath. However in mirage-scala, you can write it inline using multi-line string literal. Of course, you can also use an external file as following:

val result: List[Book] = sqlManager.getResultList(
  classOf[Book], 
  SqlFile("META-INF/selectBooks.sql"), 
  Map("author"->"Naoki Takezoe"))

mirage-scala is still under development. I'm evaluating APIs feaibility. So APIs might be changed considerably in the release version.

Mirage 1.1.2 is now available!

Mirage is a simple SQL centric database access library. See the following URL to know about Mirage:

• http://amateras.sourceforge.jp/site/mirage/welcome.html

New features in Mirage 1.1.2:

• Added DBCPSessionImpl to provide connection pooling as standalone usage.
• Added TransactionInterceptor and @Transactional for Guice Intagration.
• MockSqlManager came to support stored procedure / function.

This release does not contain so big new features. However it can be used in more large fields such as small web applications by connection-pooling in standalone usage.

I wish that Mirage helps your development. Enjoy!

AmaterasERD 1.0.8 is now available!

Project Amateras released AmaterasERD 1.0.8 at 12 February 2011.

New features in this release:

• Sybase support
• In importing and exporting, table and column comments are mapped to logical name (Oracle and Sybase only)
• Copy As Image from the context menu
• Quick Outline ([CTRL]+[O])
• Diagram font configuration
• HTML generation tool from *.erd file which could be used in command-line

See details about AmaterasERD at:
http://amateras.sourceforge.jp/cgi-bin/fswiki_en/wiki.cgi?page=AmaterasERD

See details about new features in AmaterasERD 1.0.8 at:
http://sourceforge.jp/projects/amateras/wiki/AmaterasERD_1_0_8

You can download AmaterasERD 1.0.8 from:
http://sourceforge.jp/projects/amateras/downloads/50912/net.java.amateras.db_1.0.8.jar/

Enjoy your development!

Unit Testting in Mirage

In the unit-testing for database access code, some testing frameworks such as DbUnit are available. However, as you know, to maintain test data is very painful.

Mirage proposes lightweight unit-testing without database for database access code. It's based on string matching of executed SQL and expected SQL. Executed SQLs don't reach to the database actually, they are intercepted and recorded to MirageTestContext by using MockSqlManager.

You can verify executed SQLs and these parameters through MirageTestContext as below:

@Test
public void testGetBookById(){
  // set MockSqlManager to the test target
  BookService bookService = new BookService();
  bookService.setSqlManager(new MockSqlManager());

  // configure results which would be 
  // returned by MockSqlManager.
  Book book = new Book();
  book.setBookName("Mirage in Action");

  MirageTestContext.addResult(book);

  // execute
  Book result = bookService.getBookById(new Long(100));

  // assert returned object
  assertEquals("Mirage in Action", book.getName);

  // verify the number of executed SQL
  MirageTestContext.verifySqlCount(1);

  // verify the executed SQL
  MirageTestContext.verifySqlByRegExp(0,
    "SELECT .* FROM BOOK " + 
    "WHERE ID = ? ORDER BY ID ASC", // verify SQL
    new Long(100)); // verify Parameters
}

As you see, you can also configure return values of MockSqlManager using MirageTestContext if it's necessary. You can write your test case more simple by static importing of MirageTestContext members.

Please note, the purpose of this way is not to verify whether executed SQLs are correct. It helps to find influence which is not anticipated by modification of database access code. So it requires to current database access code and SQLs are correct.

If your purpose of unit-testing for database access code is matches this concept, Mirage will decrease a cost of unit-testing and maintaining them very much.

Mirage 1.1.0 is now available!

Mirage is a simple SQL centric database access library. See the following URL to know about Mirage:

• http://amateras.sourceforge.jp/site/mirage/welcome.html

New features in Mirage 1.1.0:

Primary key generation support

• @PrimaryKey annotation has new attributes generationType and generator. The generationType attribute supports GenerationType.APPLICATION, GenerationType.IDENTIY and GenerationType.SEQAUENCE.
• The persistent attribute of @PrimaryKey annotation has been removed.

Improvement of unit testing support

• Verification methods of MirageTestContext have been enhanced.

New ConnectionProvider and Dialect

• Added JNDIDataSourceConnectionProvider and JNDIXADataSourceConnectionProvider which obtain a dada source from JNDI.
• Added MySQLDialect to MySQL support.

I wish that Mirage helps your development. Enjoy!

Mirage 1.0.6 is now available!

Mirage is a simple SQL centric database access library. See the following URL to know about Mirage:

• http://amateras.sourceforge.jp/site/mirage/welcome.html

Here is the list of changes in Mirage 1.0.6:

• Unit Testing support
  • Added MockSqlManager which is used in unit testing instead of SqlManager. See details about Unit Testing support at the UnitTest section.
• Ant Task
  • Added EntityGenTask for entity generation.

In addition, Apache Click example is updated which contains examples of TestCase using MockSqlManager. You can get it from the download page.

I wish that Mirage helps your development. Enjoy!