Re: Re: DB_Table: Summary and Pre-Call
| From: | Paul M Jones | Date: | Mon, 12 Apr 2004 15:38:17 +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-27464@lists.php.net to get a copy of this message | ||
Hi, Daniel,
But hey, I'm running the DBMS's, so some permissions settings might be more favorable to me.Exactly -- you have complete control over the target system (which is nice when you can get it :-). Many developers do not, especially those developers writing for wide distribution.
In the one application I need 100% portability,Here's where I'm coming from: when I write code, I *expect* to share it with others. Maybe it's smart, maybe it's dumb, but my default stance is that my code will end up in other hands on other systems, and I write it with that in mind (extensive inline comments, code standards, naming conventions, portable SQL, etc). In a sense, then, *all* of my applications require 100% portability. Does that limit me? Yes, in some ways. Does it have benefits of its own? Also yes. :-) I prefer that tradeoff; it might not be preferred by others. -- Paul M. Jones Savant: the simple alternative to Smarty. http://phpsavant.com/