Difference between revisions of "PostgreSQL Adapter"

From CDOT Wiki
Jump to: navigation, search
(Phase 5: PostgreSQLAdapterTest)
(Phase 5: Postgre UnitTests)
Line 49: Line 49:
 
* [[PostgreSQL Adapter-nexj/research_notes_PostgreAdapter | Research Notes]]
 
* [[PostgreSQL Adapter-nexj/research_notes_PostgreAdapter | Research Notes]]
  
===Phase 5: Postgre UnitTests ===
+
===Phase 5: PostgreSQL UnitTests ===
 
* Add database specific tests for PostgreSQL
 
* Add database specific tests for PostgreSQL
  

Revision as of 22:48, 22 January 2011

PostgreSQL Adapter for NexJ

Project Goal

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

Current Status

Project Phases

Phase 1: Investigation (DONE)

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

Phase 2: Connect to PostgreSQL server (DONE)

Phase 3: PostgreSQLSchemaManager

Phase 4: PostgreSQLAdapter

Phase 5: PostgreSQL UnitTests

  • Add database specific tests for PostgreSQL

Phase 6: Optimization

  • After implementation is done, optimizing the modified files.

Project Repository

  • 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 this information:
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