Re: SV: SV: [Phpgroupware-developers] sitemgr - setup

[Chris Weiss]

>It might be a way to build the ability to ask for reserved words into
>class.db_xxx.inc.php ?
>

my point is not everyone knows knows every db.  Some apps were written first for
MySql by someone who knows nothing of any other databases, another app for 
PGSSQL
by someone you might know MySql but not MSSQL or oracle.  How you one avoid to 
use
reserved words if they don't have a list?  Maybe we can add list of know gloabl
reserved words to the docs, but what happens when an RDBMS adds a new reserved 
word
that breaks a bunch of apps?  The answer is that we need to have the option in 
an
app to using different sql statements for each RDBMS to do escaping and such.
Here's what you can do, though this will fall into a "new feature" and will not 
get
commited to stable...or for a particular app might get commited, depending on 
the
issue it resolves:

Rename the class.so.x file to class.so.default.x, then make a new class.so.x 
that
checks to see what db is configured, then tests to see if there is a class.so 
file
just for it, if so includes it, if not includes the default file.  Make sence?  
Or
maybe Seek3r or someone more familiar with the API can suggest a better way...

What this also allows is for an app to use stored prceedures and other DB 
specific
things.  The auth classes works this way now, providing identical functions 
names
in each class but the inards of each are very different.