[Vtigercrm-developers] postgres support in v5

[Jeff Kowalczyk]

Richie wrote:
> I would suggest that we have a branch for the PostGres part so that the
> merging will be a separate operation. This will ensure that we are able
> to keep track of breakages as well.
>  
> JeffK, what do you suggest?
>  
> The core-team has been working on bug-fixes and has done quite a lot of
> changes. I am concerned that we might again have to run in circles in
> the worst case with the PostGres fixes.
>  
> Allan, no offence meant. Just voicing my concern.
> 
> Richie

Personally, I don't mind using a branch. It is extra work to maintain
(and fewer people will test), but no one wants to slow down the vtiger
teams workflow.

Allan thinks the changes (some setup changes initially, then 'ADODB/SQL
standardising' one query at a time) shouldn't cause breakage in the trunk.

If we can safely land the changeset that supports both postgresql and
mysql setup, I agree with Allan that there should be very little impact on
mysql users from the per-query changesets. If there's a problem, just back
that changeset out and ref #752.

If the original plan is resumed to make a
vtigercrm/branches/5.0_postgresql_integration, I will volunteer to naively
merge (e.g. trunk wins conflicts, annotated) incoming trunk changesets to
the postgresql branch during the few days while Allan, Joel and Michel's
postgresql work is being done.

FWIW, we could try the development in the trunk, and branch at any time if
problems arise. I expect that after the postgresql setup capability is
added, there won't really be a need to branch.