PostgreSQL Adapter

PostgreSQL Adapter for NexJ

Project Goal

Develope an adapter to enable NexJ Express model to interact with PostgreSQL database

Current Status

Dec 2010
Database 'test' is created in Postgre. sample table 'mutex' is created for testing the connection properties. No need for SET SQL mode in Postgre Creating tables in process Tables are created. Creating indexes and triggers in process

Nov 2010

Walk through parts of code related to SQLadapter, SqlSchemaManger and setup scripts in NexJ Express code SQLAdapter (src, test) and SQLSchemaManager (src, test) classes are extended to create PostgreSQL classes Proper PostgreSQL Driver is installed. Postgre package url for XADataSource is added to the related files. cofig and connection files are modified based on Postgre properties Application is now connected to the Postgre database.

• TODOs

Project Phases

Phase 1: Investigation

• Get requirements from NexJ (Meeting on Friday Nov 5th)
• Walk-through the code
• Familiarization with PostgreSQL

Phase 2: Connect to PostgreSQL server

• Connect to PostgreSQL server

Phase 3: PostgreSQLSchemaManager

Extend SQLSchemaManager to support PostgreSQL.
SQLSchemaManager is used in maintaining database schemas (DDL)

Phase 4: PostgreSQLAdapter

Extend SQLAdapter to support PostgreSQL.
SQLAdapter is used in manipulate data in existing schemas (DML)

Phase 5: Test properties specific to PostgreSQL

• Add test cases that are specific to PostgreSQL database

Phase 6: Optimization

• After implementation is done, optimizing the modified files.

Project Repository

• URL for central repository of the project is: http://liberia.proximity.on.ca:81/

• Steps to work with the repository

1- Follow the instructions to create the NexJ Express workspace from the manual.

2- After creating 'ws' directory, open Eclipse and click on File -> Import -> Mercurial -> Clone Existing Mercurial Repository -> Enter these information to clone from repository:

URL: ssh://liberia.proximity.on.ca/mercurial/postgreSQL/core

Username: developer

Clone directory name: core

3- The central repository's structure is:

Main branch called 'default'

New branch or branches with this naming convention: 'wsComitter' e.g. 'wsMinoo'

4- After cloning the project, follow these steps to add a new branch with your user name:

First make sure the active branch is 'default'. Notice the top of the Package Explorer e.g. core[5:b8b2f102343@default(tip)]

Right click on 'core' in the Package Explorer

Click on 'Team' -> Add Branch

Enter the branch name in the box -> Finish

Enter the commit message -> OK

Check the 'Force Push' if applicable.

Now the branch name at the top of Package Explorer is changed to the new branch name.

5- To switch to a different branch, choose 'Switch' instead of 'Add Branch'

• NOTE! To avoid any conflict, do the 'Pull' every day and before any push.
• NOTE! First just 'Commit' changesets and do not 'Push' them until the end of the day or the time you are confident by latest changes to the code, then 'Push' them all at once and 'Merge' them with the 'default' branch in central repository.

Resources

• Intro

Concept of Adapter [1]

FOSSLC PostgreSQL

• Java
• Database & Persistence
• JDBC
• PostgreSQL Specifications
• MySQL Specifications
• Postgre - MySQL Compare