Re: DB stuff

I second what Rasmus wrote. That type of functionality isn't really what a language itself should be about. Now, what you're comparing it to (application servers) AREN'T just 'languages' - they bill themselves as having the ability to do bigger and better things. By all means use them if you need that stuff. 300 users on a MySQL database? If you've got good hardware, shouldn't be that much of an issue. Prioritize? I'd say first come first served. Properly done queries (optimized, etc.) should be a small fraction of a second, so the idea of hundreds of users shouldn't be too taxing - ideally they'd be idle a lot of the time. If you're looking for load balanced databases, and you truly need it, you possibly should be looking at something more robust anyway (not starting a MySQL flame war here, but it's not the be all and end all of the universe!) "Voitenko, Denis" wrote: > I agree with you on most points. I myself use custom DB abstraction. Now try > putting 300 users on your MySQL database. What happens? Even an SMP box > starts begging for forgiveness. How would your prioritize your queries, put > them in a queue or load balance a couple of database servers? > > -----Original Message----- > From: Michael Kimsal [mailto:michael@tapinternet.com] > Sent: Tuesday, November 07, 2000 8:27 AM > To: Voitenko, Denis > Cc: 'php-general@lists.php.net' > Subject: Re: [PHP] DB stuff > > You're stirring up a hornet's nest here... :) Go read the archives > (link to archive sites are found on php.net under 'support' I think). > > Couple things to keep in mind here - first off, PHP isn't an application > server - it's a scripting language. This isn't a putdown of PHP, but you > gotta > remember that PHP was doing stuff before many of the people at > these larger companies had even heard of the internet. > > Second, there are abstraction layers that you can use in PHP to > give that you independance. It's at a (slight?) speed decrease. By > coding using native drivers and coding for the specific database, > you can (so the story goes) get more performance out of the application. > That's been my experience as well. > > This isn't meant to flame people working on DB abstraction stuff (we've > done our own in house as well, which also support query results caching) > but honestly, how many times do you switch databases in the middle of a > project? If you've spent how many thousands on weblogic, do you > change DBs in midstream that often? > > If you've gotta configure things in the 'guts' on weblogic, I can do pretty > much the same thing by changing about 3 lines in an include file. > > "Voitenko, Denis" wrote: > > > I am wondering why wouldn't PHP support database connectivity like most > > application servers do, e.g. something like a data source in JRun or > > WebLogic where database connectivity is made DB server independent and all > > the DB connectivity is configured in the guts of PHP? > > -- > ========================== > Michael Kimsal > http://www.tapinternet.com > 734-480-9961 -- ========================== Michael Kimsal http://www.tapinternet.com 734-480-9961