Projects tagged ‘jdbc’ and ‘orm’

A lightweight object-relational bridge for Java, based on (and mostly compliant with) the "Ease of Development" API distributed with Java 6 beta.

The page has moved.The page you are trying to access has been moved here. Please update your bookmarks. Thank you.

The JAVA library which reconciles JDBC and POJO. Start working with POJO without rewriting all your JDBC application. Without any configuration file, without any annotation, use your native SQL request with JDBC and get POJO(s).

Generic Dao is a Java package which allows a developer to skip writing DAOs for their persistent objects when they are using Spring and JDBC or Hibernate (support for others as needed/requested). It ... [More] provides basic DAO methods like save/create/delete/update/findById, search methods, and batch update methods for ORM functionality which stays out of your way. It can easily be overridden and controlled. Interceptors and caching mechanisms are provided. This also includes a set of reflection utilities which allow for Commons BeanUtils like functionality but includes support for annotations, fields, construction of any object, and nested null handling. [Less]

The goal of this project is to create a standalone, command line based application that mirrors as close as possible the power of ActiveRecord Migrations. Commands should allow for creation of ... [More] universal XML based migration files that mirror the syntax of current ActiveRecord Migrations files. With these xml files, the program will be able to create SQL, Mapping files, and/or Model classes. Design will be modular such that additional database support and persistence framework support can be easily added in a plug-in like manor. Initial database/persistence framework support will be PostgreSQL/Hibernate3 with the plan to add support for mySQL, SQL Server and Torque in the near future. [Less]

Relational-Object Mapper Is Not Object-Relational For those who model the database first, and don't want to hide the fact that they are talking to a relational database engine. The project's aim ... [More] is to ease the use of database entities and the representation of database data as java beans. The code will be based on JDBC and the DAO pattern. In the future, it's expected that a code generator will be also provided. This project assumes you are very concerned with your database design, write most of your queries within stored procedures, and don't want any traditional ORM in between. WARNING: The result of this project might not be scalable, might not be clusterable, and might not be your best option. You have been warned !! [Less]

nanorm is a simple and lightweight data mapper framework inspired by the Apache iBatis. It is not meant to be an full ORM solution. The main features are: Strict typing where possible Easy to use ... [More] Easy to mock in unit tests Low performance overhead compared to hand-written JDBC mapper Latest Changes0.4.3, released 2009-07-16Added ability to enable/disable auto-session support. Note that auto-session is disabled by default starting from this version (so you should open session explicitly or turn it on via call NanormConfiguration#setAutoSessionEnabled(boolean)). Fixed  issue #18  Minor code style impromevents and JavaDoc updates 0.4.2, released 2008-11-08Moved TypeHandler from the internal package to the API package Added support for mapping result set to result object directly via TypeHandler (@Scalar annotation) Configuration validation improved. Several minor issues fixed 0.4.1, released 2008-10-19Added two new type handlers, for byte and java.util.Locale. Some methods were renamed in public interface DataSink Fixed issue with wrong caching of setters used for setting pre-generated keys Fixed issue with incorrect getters/setters lookup (didn't searched in inherited methods) Fixed issue with handling arrays of primitive types Using with Maven2Add this repository entry to repositories section of Maven POM: nanorm-releases-repo Repository on code.google.com http://nanorm.googlecode.com/svn/maven2/releases/ false Then add this dependency entry to your Maven POM to include nanorm in your project: com.google.code.nanorm nanorm 0.4.3 Sample codeDeclare an interface: public interface CarMapper { /** * Get car by id. * Declare a mapping. In this case it is automatic, meaning that properties * not explicitly mapped will be mapped to the columns with same name. * Explicitly map owner column to ownerName property. */ @ResultMap(id = "car", auto = true, mappings = { @Mapping(value = "ownerName", column = "owner") }) @Select("SELECT id, model, owner, year FROM cars WHERE ID = ${1}") Car getCarById(int id); }Car is a POJO with id, model, year and ownerName properties. Using the mapper: NanormFactory factory = ... // Create factory Connection conn = ... // JDBC connection CarMapper mapper = factory.createMapper(CarMapper.class); // Make factory to use this connection for current thread Session sess = factory.openSession(conn); try { Car car = mapper.getCarById(1); // Use it ... sess.commit(); } finally { sess.end(); } [Less]

samurai-dao is a simple, high performance object/relational persistence and query service. O/R Mapping. No XML. Two Way SQL. Run with Java. Run with SQL Client. Sample code: List empList = dao.select(ALL, Employee.class);

Snap ORM is intended to be a high speed Object Relational Mapping framework that avoids using techniques like class proxying that slows down conventional ORM tools like Hibernate

Faster development. Full flexibilityFull freedom on class design. O/R Broker does not place any limitations on how you design your classes. No restrictions whatsoever. You write the SQL. This allows ... [More] you to hand tune any query and from personal experience, is as fast (if not faster) than configuring some obscure XML file. You write the query-to-object mapping code in Scala (or Java). No tired XML mapping needed. SQL can be in code or, preferably, in simple text files, ready for editing and optimizations if needed. SQL can be dynamic through either Velocity or FreeMarker template engine syntax. Both are supported, but none are required. Dealing with new database schema, legacy schema, JavaBeans, or immutable classes? All possible, full flexibility. [Less]