Projects

Hibernate Tools

Working with Hibernate is very easy and developers enjoy using the APIs and the query language. Even creating mapping metadata is not an overly complex task once you've mastered the basics. Hibernate Tools makes working with Hibernate or EJB 3.0 persistence even more pleasant. Hibernate Tools ... [More] is an entirely new toolset for Hibernate3 (see this page for an overview of the Hibernate 2.x toolset), implemented as an integrated suite of Eclipse plugins, together with a unified Ant task for integration into the build cycle. Hibernate Tools is a core component of JBoss Tools and hence also part of Red Hat Developer Studio. See the documentation and screenshots for more information or download Hibernate Tools now! [Less]

CDO Model Repository

claimed by Eclipse Foundation

CDO Model Repository ===================== CDO is both a development-time model repository and a run-time persistence framework. Being highly optimized it supports object graphs of arbitrary size. CDO offers transactions with save points, explicit locking, change notification, queries ... [More] , temporality, branching, merging, offline and fail-over modes, ... The storage back-end is pluggable and migrations between direct JDBC, Hibernate, Objectivity/DB, MongoDB or DB4O are seamless for CDO applications. [Less]

Puzzle-GIS

The main goal of Puzzle GIS is to create a free, multiplatform (Java based), production ready and competitive tool as a valid alternative to commercial software. This application is a GIS development platform based on NetBeans 6.

Business Logic Toolkit for .NET

Business Logic Toolkit is a set of components to simplify .NET application development. BLToolkit is provided as source code that you can use "as is" or customize for your applications. It is written in C# and compatible with .NET Frameworks 3.5 and 4.0, Silverlight 4, and Mono.

WKTRaster

Raster types for PostGIS. PostGIS WKT Raster is an ongoing project aiming at developing raster support in PostGIS. The goal of WKT Raster is to implement the RASTER type as much as possible like the GEOMETRY type is implemented in PostGIS and to offer a single set of overlay SQL functions ... [More] (like ST_Intersects) operating seamlessly on vector and raster coverages. [Less]

pdoMap - PHP ORM & Persistance Layer

pdoMap is a robust php ORM with a lot of OOP functionalities. The mapping structure, requests, or transactions are defined in XML files. The core generates PHP directly classes for high performance. It's verry easy to use and configure : - Map (or generate from existing database) ... [More] the database tables under a structured XML file - Define Requests and Transactions on XML language (fully database portable) - Easilly extending entities or adapters class with your code - Functions to deploy database or synchronise structure Other functionalities : fully optimised code, caching data, full lazy loading system, open system for extending all functionalities ... [Less]

Tenor Framework

The Tenor Framework is a set of utilities to improve development of web projects, although it can be used on desktop projects. The main goal is to simplify mapping relational tables to entities, in a simple and maintainable way.

Natural Resources Database - GIS

NRDB Pro is a GIS tool enabling environmental and socio-economic data to be stored and distributed as a single database. It supports the import, digitising, encoding and export of spatial data and the production of maps, graphs and reports.

nanodotnet

Nano is an ORM (Object Relational Mapping) library for use with .NET applications. It is simple and easy to use. By using class and property attributes it provides a way to map objects to database tables.

dbix-entityrecord

Target FeaturesDBIx namespace implies DBI-based data layer DataMapper based ORM Better encapsulation via inside-out objects Basic CRUD create retrieve update delete Relationships (associations) such as: one_to_one - reference one_to_many - "has many" style many_to_one - "belongs ... [More] to" style many_to_many Identity Map - track objects and make sure only one copy exists + update if needed Let the database handle data consistency (and if necessary, validation) RaiseError=1 .. "Bubble up" exceptions on data inconsistency (esp. on constraint errors) Object Modelling should follow the OOAD practice of: Design the Domain Model schema (entity classes), they comes first Design the RDBMS schema, to reflect your domain model, here we enforce constraints and validation as needed based on the Domain Model Be a thin abstraction layer while allowing low-level access as well CPAN release Why another ORM for Perl?Enforce that Domain Models should not have any knowledge on the persistent store Database concrete artifacts (e.g. tables, columns, keys) should not be visible to the domain model Use of Mapping: Classes=>Tables, attributes=>columns ... (assumes type system) DataMapper provides better reusability for Domain Models (loosely coupled) DataMapper provides better testability for Domain Models (e.g. without hitting the database) InsideOut objects provides encapsulation needed for non-destructive inheritance TIMTOWTDI Because doing such project can help us learn and understand stuff (on top of actually attempting to solve a specific problem) Interested?Check out the source, poke around Email me dexterbt1 AT yahoo.com Check out the wiki [Less]