The generated source code uses standard JDBC methods for persistence, and there is no runtime library required. Mapping Philosophy Different object-relational mapping tools have different philosophies about how to do the mapping. Some tools are very flexible, and allow you to combine fields from multiple tables to form a single class. Others don't generate source code, but instead rely on a configuration file, and generate dynamic SQL at runtime. This class provides lifecycle methods for loading, saving, and deleting rows in the table.
Managers are singletons in the system.
All Manager classes descend from a Manager base class that you will customize after the first time you run the mapping tool. This base class dispenses JDBC connections to the managers, and serves as a place where you can stick utility code that managers should have access to. Testing was done with version 1.2c of the mm driver . Unlike the Oracle support, which I've tested on production code on a work related project, the MySQL support has only be tested with the StoreClientMysql class. Unfortunately, I haven't been able to keep everything up to date.