[Vtigercrm-developers] An Impassioned Plea from an VTiger Integrator

[Matthew Brichacek]

I have started doing the query part as I run into them in my branch.
I'm also moving the query strings out of functions like get_leads() and
putting it in get_related_leads_query() instead.  This way the query can
be used for other things.. like for example if you want mostly the same
output of get_leads() but without the HTML that manged to find its way
out of the presentation layer and into the data layer... don't get me
started on that.
Anyways, with the HUGE db query strings that are used in the system,
breaking them into separate short lines is a great suggestion for
manageability and if it makes merges easier it's like getting your cake
and eating it too :).

Matt

On Wed, 2006-07-12 at 10:06 -0400, Jeff Kowalczyk wrote:
> Dennis Grant wrote:
> > Actually, I think with VTiger you are going to see a lot of private
> > forks, because individual businesses have their own needs and wants that
> > are supersets of core VTiger functionality that simply don't apply to
> > other businesses.
> 
> This is one of the reasons why I care about making the source more
> merge-friendly (particularly short, vertically formatted SQL statement
> string lines).
> 
> If we can get the codebase to the point where branching and merging is a
> manageable burden, customization branches have a fighting chance to be
> maintained in the repository. Or use a distributed repository such as
> bazaar-ng can be used (bzr has a trac backend now).
> 
> 
> _______________________________________________
> Get started with creating presentations online - http://zohoshow.com?vt