I am a software developer. I think that this project might be useful to me, however, I only use PostgreSQL. PostgreSQL, in my usage of it, functions more as an application framework as opposed to a mere database, so that is my only option. Should I fork nuBuilder2 and replace all of the MySQL PHP calls with PostgreSQL calls and update the syntax, or would you like for me to help with PostgreSQL support in nuBuilder3?

Thanks. I saw those as I was doing my research on this project/product. I added PostgreSQL support to SugarCRM over a weekend many years ago; long before their new abstraction layer was in. So I have done this before. While the port was successful, SugarCRM never got around to giving me the ability to contribute my code back to them. The issue was that they required copyright assignment of all contributed code to them so that they can relicense that code in conjunction with their paid non-open source enhancements. I had called and sent e-mails, but one of the persons who I was forwarded to never got back to me. So I prefer to avoid this type of hassle.

I would love to help make PostgreSQL support for version 3 stable by the time that they are ready to do a formal release, but if that development process is closed to me, then I cannot help. Forking version 2 should not take much longer than what I did for SugarCRM in the past, but I prefer not to maintain a fork all by myself. I hope to have one of these two versions stable before the end of the year. Since my work inherently involves testing a lot, I could potentially help speed up the testing process too. I plan on adding PostgreSQL specific features, such as: Full text search, bitemporal tables, foreign data wrappers, and database level timezone awareness.