<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body >Hi!
<br>
<br>Team, we need volunteers to help us provide the postgres support. We are running short of hands here and we need help.
<br>
<br>I would like to know how to start approaching this - right from the start of the installation procedure.
<br>I would prefer to have a plan-of-approach in place by the PostGres gurus and then move ahead based on their advice. Also, an indication of the time required to achieve the same will be helpful in further planning.
<br>
<br>I repeat, we are held up here with the bug-fixes and are not able to devote any time to PostGres. We need help.
<br>
<br>Thank You,
<br>Richie<br><br><br><br><br>---- Jeff Kowalczyk<jtk@yahoo.com> wrote ---- <br><br><blockquote style='border-left: 2px solid #0000FF; padding: 6px;'><html>
<xbody>
Just to see what an automatic merge would accomplish to bring the 4.2<br>postgresql support to the trunk, I did a dry run merge. Definitely file<br>this under 'foolhardy merging that would break the trunk in many ways':<br><br>In svn update/merge console output, 'U' indicates clean merge of<br>changesets, 'C' indicates conflicting lines.<br><br>This merge testing is done with a trunk checkout:<br><br> URL: <a href="http://jeffk@vtiger.fosslabs.com/svn/vtiger/vtigercrm/trunk">http://jeffk@vtiger.fosslabs.com/svn/vtiger/vtigercrm/trunk</a><br> Revision: 5506<br><br>Changeset 5306 is the changeset that merged the work from<br>vtigercrm/branches/4.2_postgresql_integration to the 4.2 branch.<br><br>The following files would apparently get clean automatic merges of the<br>changeset that adds postgresql support to branches/4.2:<br><br> $ svn merge --dry-run<br> <a href="http://jeffk@vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/4.2@5305">http://jeffk@vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/4.2@5305</a><br> <a href="http://jeffk@vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/4.2@5306">http://jeffk@vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/4.2@5306</a> |<br> grep 'U ' <br> U modules/Reports/SaveReportFolder.php<br> U modules/Reports/Save.php<br> U modules/Reports/Reports.php<br> U modules/Settings/SaveConvertLead.php<br> U modules/Settings/DeleteCustomField.php<br> U modules/Settings/UpdateComboValues.php<br> U modules/Users/User.php<br> U modules/Users/massdelete.php<br> U modules/Users/updateLeadDBStatus.php<br> U modules/Calendar/appointment.pinc<br> U modules/Import/UsersLastImport.php<br> U include/database/PearDatabase.php<br> U schema/DatabaseSchema.xml<br><br>This definitely doesn't mean complete support (in these files) for<br>postgresql, only that the changesets from the branch would cleanly merge<br>to the trunk without additional effort.<br><br>These (many) other files would have conflict lines added to the source.<br>This would definitely bring PHP syntax breakage, and require immediate<br>attention to resolve the conflicts before the code would even run again:<br><br> $ svn merge --dry-run<br> <a href="http://jeffk@vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/4.2@5305">http://jeffk@vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/4.2@5305</a><br> <a href="http://jeffk@vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/4.2@5306">http://jeffk@vtiger.fosslabs.com/svn/vtiger/vtigercrm/branches/4.2@5306</a> |<br> grep 'C '<br> C config.inc.php<br> C modules/Accounts/ListViewTop.php<br> C modules/Accounts/Account.php<br> C modules/Accounts/Popup_picker.php<br> C modules/Accounts/Popup.php<br> C modules/Accounts/ListView.php<br> C modules/Quotes/Quote.php<br> C modules/Quotes/Delete.php<br> C modules/Quotes/Popup.php<br> C modules/Quotes/ListView.php<br> C modules/Potentials/Popup.php<br> C modules/Potentials/ListView.php<br> C modules/Potentials/Opportunity.php<br> C modules/Leads/Popup.php<br> C modules/Leads/Lead.php<br> C modules/Leads/ListView.php<br> C modules/Leads/LeadConvertToEntities.php<br> C modules/Home/UnifiedSearch.php<br> C modules/Notes/Delete.php<br> C modules/Notes/ListView.php<br> C modules/Invoice/Invoice.php<br> C modules/Invoice/ListView.php<br> C modules/Reports/ReportRun.php<br> C modules/Reports/PopulateReports.php<br> C modules/HelpDesk/HelpDesk.php<br> C modules/HelpDesk/ListView.php<br> C modules/Users/SaveProfile.php<br> C modules/Users/SaveOrgSharing.php<br> C modules/Users/LoginHistory.php<br> C modules/Users/saveemailtemplate.php<br> C modules/Users/ListView.php<br> C modules/Users/Security.php<br> C modules/Users/SaveRole.php<br> C modules/Products/Popup.php<br> C modules/Products/AddProductsToPriceBook.php<br> C modules/Products/ListView.php<br> C modules/Products/Delete.php<br> C modules/Products/Product.php<br> C modules/Activities/Activity.php<br> C modules/Activities/ListView.php<br> C modules/Activities/RenderRelatedListUI.php<br> C modules/Activities/OpenListView.php<br> C modules/CustomView/Save.php<br> C modules/CustomView/CustomView.php<br> C modules/Faq/ListView.php<br> C modules/uploads/add2db.php<br> C modules/Emails/Email.php<br> C modules/Emails/ListView.php<br> C modules/Contacts/Contact.php<br> C modules/Contacts/Popup.php<br> C modules/Contacts/ListView.php<br> C data/CRMEntity.php<br> C data/SugarBean.php<br> C include/RelatedListView.php<br> C include/PopulateComboValues.php<br> C install/5createTables.inc.php<br> C install/4createConfigFile.php<br> C install/1checkSystem.php<br> C install/2setConfig.php<br> C install/populateSeedData.php<br> C install/3confirmConfig.php<br> C adodb/adodb.inc.php<br> C adodb/adodb-lib.inc.php<br> C adodb/drivers/adodb-mysql.inc.php<br><br>There are a few skipped files, due to move, rename or removal in trunk.<br><br>Again, merging and subsequently resolving these many conflicts would by no<br>means imply completed postgresql support for the trunk.<br><br>However, any approach that brings the trunk and maintained branches closer<br>together would be a positive thing.<br><br>Once vtigercrm-5.0.0 is in production, certainly people will want to<br>back-port selected features, and forward-port bug fixes during the long<br>lifecycle of the vtigercrm-4.2.x series. Minimizing diffs between<br>branches always makes that process easier.<br><br>Just FYI. I don't think this merge (except for the 'U' files) would do<br>any good at this point. Allan can probably move through the trunk codebase<br>quicker with his method.<br><br><br>Note: svn revert doesn't undo conflict messages AFAICT. If you try this<br>merge without the --dry-run option, be prepared to check out a fresh trunk<br>working copy after you are done examining the results.<br><br>_______________________________________________<br>This vtiger.com email is sponsored by Zoho Planner. Still scribbling down your To-Do's on bits of paper & palms of your hands? Try the AJAX enabled, personal organizer online, Zoho Planner for FREE instead! <a href="http://zohoplanner.com/?vt">http://zohoplanner.com/?vt</a> <br>
</xbody>
</html></blockquote></body></html>