[Vtigercrm-developers] PostGres support

[Allan Bush]

I think most people have the right idea here, we don't want to support
mysql 4.1 or 5.0 or postgres or any other database.  Just like writing
w3c complaint html we want to write SQL (probably 92) compliant
statements and then add any vendor specific hacks as they are needed.

As mentioned I don't think those libraries are what we want (that
would just add one database to the list of supported dbs), using adodb
is a good start, but if the SQL needs to be standard as well.

What does that mean to mysql programs? Basically just don't do
anything on this (http://sql-info.de/mysql/gotchas.html) list, and we
are doing a lot of that right now.

On 1/9/06, Tim Smith <vtiger at timandjulie.com> wrote:
> In a former product, we took the approach of using standard, simplified SQL
> across the majority of SQL statements with macros/escaping to handle vendor
> specific issues.
>
> For example:
>    Select a, b + c from tablex
> Would become:
>    Select a, b {@+@} c from tablex
>
> {@+@} would be replaced with the vendor specific concatenation command.
> (This was required for Oracle)  A centralized sql execution function would
> determine the target database and replace macros before executing.
>
> Using these macros, we handled differences in:
> * String concatenation
> * Date comparison
> * Case sensitivity in queries
> * Joins
>
> In about 2% of our code, we required vendor specific optimizations or bug
> work arounds.  These were the only kludges required.  Otherwise, macros
> dealt with all differences.
>
> Regards,
> Tim
>
> Onweald, Inc.
>
>
> -----Original Message-----
> From: vtigercrm-developers-bounces at lists.vtigercrm.com
> [mailto:vtigercrm-developers-bounces at lists.vtigercrm.com] On Behalf Of
> Sergio A. Kessler
> Sent: Monday, January 09, 2006 6:19 AM
> To: Richie
> Cc: vtigercrm-developers at lists.vtigercrm.com
> Subject: Re: [Vtigercrm-developers] PostGres support
>
> yup, but vtiger uses ADODB,
> it shouldn't be hard to ensure that the queries also work in postgresql...
>
> and if the queries are developed with the sql standards in mind, the less
> porting work is needed...
>
> /sak
>
> On 1/9/06, Richie <richie at vtiger.com> wrote:
> > Hello!
> >
> > Came across this article on PostGres movement.
> > Joel,bushwack you guys might be interested
> >
> > http://software.newsforge.com/software/05/12/15/1611251.shtml?tid=72
> > _______________________________________________
> > vtigercrm-developers mailing list
> > vtigercrm-developers at lists.vtigercrm.com
> > http://lists.vtigercrm.com/mailman/listinfo/vtigercrm-developers
> >
> >
> >
>
> _______________________________________________
> vtigercrm-developers mailing list
> vtigercrm-developers at lists.vtigercrm.com
> http://lists.vtigercrm.com/mailman/listinfo/vtigercrm-developers
>
> _______________________________________________
> vtigercrm-developers mailing list
> vtigercrm-developers at lists.vtigercrm.com
> http://lists.vtigercrm.com/mailman/listinfo/vtigercrm-developers
>