BeanKeeper 2.6.0 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News BeanKeeper 2.6.0 (Default branch)
# 1  
Old 02-02-2009
BeanKeeper 2.6.0 (Default branch)

BeanKeeper (formerly Simple Persistence for Java) is a full featured, powerful object/relational persistence and query library. It has a unique philosophy of simpleness and ease of use: it does not require config files, annotations, code generation, code "enhancing", or any kind of tools to be used. It handles simple Java beans (or POJOs) and its query service returns lists. Despite its simpleness, under the hood the library takes care of all the necessary logic: transaction visibility, result list paging, keys and ids, table creation/modification, class relations, inheritance/polymorphism, case sensitiveness, and much more. It currently supports: Oracle, HSQLDB, MySQL, and PostgreSQL. License: GNU Lesser General Public License (LGPL) Changes:
Java-cup was replaced with JavaCC for parser generation. JUnit was replaced with TestNG. Ant was replaced by Maven2. One memory leak bug was fixed. The code was cleaned up to pass the checkstyle audit. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
Tangram::Driver::Pg(3pm)				User Contributed Perl Documentation				  Tangram::Driver::Pg(3pm)

NAME
Tangram::Driver::Pg - Orthogonal Object Persistence in PostgreSQL databases SYNOPSIS
use Tangram; use Tangram::Driver::Pg; $schema = Tangram::Driver::Pg->schema( $hashref ); Tangram::Driver::Pg->deploy($schema, $dbh); $storage = Tangram::Driver::Pg->connect( $schema, $data_source, $username, $password ); $storage->disconnect(); Tangram::Driver::Pg->retreat($schema, $dbh); DESCRIPTION
This is the entry point in the Pg-specific object-relational persistence backend. This module performs the following: METHODS
This backend does not add any methods; for a description of available methods, see Tangram::Relational. ERRATA
Tangram::Type::Dump::Storable objects are first encoded with MIME::Base64, because Tangram does not currently have an easy mechanism for calling "DBI->bind_param()" at the appropriate time to flag the column as binary. Tangram::Type::Dump::Perl objects are stored as "BYTEA" columns, which as of DBD::Pg 1.31, also do not get correctly escaped by the DBD driver. This also affects the (as-yet not fully functional) Tangram::Type::Dump::YAML back-end, which might put "" characters into a YAML document. It is recommended to use the "storable" type with Tangram::Type::Dump::Any for this reason. perl v5.8.8 2006-03-29 Tangram::Driver::Pg(3pm)