Re: Re: DB_Table: Summary and Pre-Call
| From: | Lukas Smith | Date: | Mon, 12 Apr 2004 15:33:51 +0000 |
| Subject: | Re: Re: DB_Table: Summary and Pre-Call | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-27463@lists.php.net to get a copy of this message | ||
Daniel Convissor wrote:
On Mon, Apr 12, 2004 at 10:04:20AM -0500, Paul M Jones wrote:well this is exactly that the datatype abstraction is about in MDB[2]. I was however also thinking about adding some sort of function abstraction, but never got around to thinking about it in more detail. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07One problem is that the solutions you note on that page require in some cases that the end-user be able to control the database system settings.I don't think that's an issue. All one needs to do is issue a particular query which alters one's own session -- or at least that's how it seems to have worked for me while I was testing. But hey, I'm running the DBMS's, so some permissions settings might be more favorable to me.Another problem as it relates to DB_Table is that a query written for, say, Oracle (using the TO_CHAR function to convert from the native date format to ISO standard) will not work for Microsoft SQL Server (which uses a DATEFORMAT function).In the one application I need 100% portability, I've created a method which detects which DBMS is being used (via 'phptype') and then returns the appropriate formatting clause which then gets used in the query string. I'm thining of adding something similar to DB.