The moment I started to use such toolkit, I have choices to move my stuff to
different database/webserver without major disruptions. As soon as I start
to use intricate features of specific database I limit my database choices
to that database. If your stuff really requires some specific features, I
don't think any toolkit will help you.
Wrong, IMHO. A toolkit that specifically takes advantages of a
particular database will help you.
It will make a more powerful toolkit.
Personally I want to write in standard SQL. The only problem is there is no
such beast in existence. All databases have incompatible quirks.
PostgreSQL (and DB2) have the closest dialect to the standard.
PostgreSQL's main mission
is to provide an SQL standard database.
I use what DreamHost provides: 1.x. If you think this is a wrong choice,
feel free to write them. I did. Ditto for mod_deflate. I don't think it is
relevant for my needs.
You said you wanted gzip capability mod_deflate with Apache 2 will give
that to you and probably
eliminate your issue. That is all I was saying.
As I said, MySQL is a horrible database. I am a PostgreSQL Advocate. If
you need decent database hosting, come over here
(http://www.commandprompt.com). We won't even let you install MySQL.
So much about choices. :-) "We'll force people to Communism with an Iron
Fist" (c) Reds --- who knew exactly what is best for the people. :-)
Command Prompt is a PostgreSQL company. We don't have to give you
database choice.
If you want database choice there are plenty of other providers :)
You did mention "MySQL is a horrible database" twice. Does it mean that
everybody should concentrate on one database de-jour? Today it is
PostgreSQL. Yesterday it was MySQL.
No. It was only MySQL to the uniformed. Any real database person knows
that MySQL
is a horrible database (well at least for anything OLTP, it isn't bad if
you just want to
throw a web site up).
Before that it was Oracle. IBM is
touting DB2, and so on. I don't even know what is going to be tomorrow.
Beefed-up SQLite on steroids? :-)
Well I was speaking to Open Source. Oracle and DB2 are also pretty good
databases.
Personally I think that people have to have a choice. Let's be pragmatics
for a change.
Yes lets. Lets make sure we don't screw up a great piece of software by
making a huge
abstraction layer that will only hurt the performance, reliability and
feature richness
of the product.
For example, I never really understood a reason why people use
SQLite,
Actually I do understand that. It is a great little embedded database.
As long as you use
it for what it is meant for.
Thank you for your kind permission to waste my resources. I feel less guilty
now.
Glad to hear it :).
In regards to IIS, that is probably lack of expertise more than anything.
;-)
Actually no. I have a great deal of IIS expertise, more than I would
ever care to admit in real life.
I speak from many hours of pain, torture and tears.
PS: I never understood what "runs natively" means. "PostgreSQL runs natively
on Windows XP. Apache runs natively with Windows XP." Is there any other
way? Either it runs or it doesn't. Probably my lack of expertise is acting
up again...
PostgreSQL used to require an emulation layer called Cygwin. Basically
it was a psuedo-unix
system (libs, shell) on top of Windows.
So you would be running Windows->Cgwin->PostgreSQL.
Now it is just Windows->PostgreSQL
Sincerely,
Joshua D. Drake
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
