PostgreSQL Adapter
PostgreSQL Adapter for NexJ
Project Goal
Develop an adapter to enable NexJ Express model to interact with PostgreSQL database
Supported Versions
- 8.4
- 9.0
Current Status
- Phase 8
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 (DONE)
- Estimated Duration: 3 weeks (Jan 17 - Feb 11, 2011)
- Extending SQLSchemaManager
Phase 4: PostgreSQLAdapter (DONE)
- Estimated Duration: 3 weeks (Feb 14 - 25, 2011)
- Extending SQLAdapter
Phase 5: PostgreSQL UnitTests and Optimization (DONE)
- Estimated Duration: 2 weeks (Feb 28 - Mar 11, 2016)
- Add database specific tests fostr PostgreSQL
- test for required contrib scripts
- test for custom blob read & write functions
- Add PostgreSQL specific optimization
Phase 6: Test with NexJ Express Studio (DONE)
- Estimated duration: Mar 7- Apr 14, 2011
- Run model in Express studio using the postgresql adapter
- create scripts for database initialization, creation and dumping
- create scripts for JBoss
- Deploy to JBoss
Phase 7: Megre Code with Latest Revision (DONE)
- Merge code with lastest revision from http://mercurial.nexj.com/express
Phase 8: Code Review
- Estimated Duration: Apr 14,2011 -
- Send Code to NexJ For Review
Project Repository
- URL for central repository of the project is: https://bitbucket.org/gbatumbya/postgresql_external
- 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:
- 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.