Re: PostgreSQL Advocacy, Thoughts and Comments

Thanks, Tony

It's good to hear that my article hasn't fallen on deaf ears (er...
rather... blind eyes). I wrote this article as a result of reading many
messages in the pgsql mail archives wishing for such a thing. I also
intended to write another article (actually, a series of articles) to be
distributed freely for online use, and not focusing only on PHP. I am
still working on this, but a recent job change and an urgent project
have slowed me down a little. I plan to have at least a couple of these
ready before the new year, when I will post links to them here
(actually, in the pgsql-advocacy), and will welcome any reviews,
criticism, etc... I will also be more than happy to participate in any
way (reviews, proofreading, etc...) for any others writing articles.
Count me in, as a (more than) happy PostgreSQL user.

And yes, I think you hit the nail on the head here: often those who are
very familiar with PostgreSQL don't realize just how little
understanding many developers have of its potential. Since I was, until
2-3 years ago, an 'outsider' to many of the serious concepts of the
relational model, I can empathize with them somewhat, and it has helped
me present the case.

I was recently made moderator of the Database section at Dev Shed
Forums, where I have hopefully had a hand in explaining PostgreSQL to
more than a few developers. Based on what I am seeing, I sincerely
believe PostgreSQL is going to get LOT more recognition over the next
couple of years. This is especially the case if a few of us start
presenting *positive explanatory material*, in addition to the
comparisons to other DBMSs. The sad fact is, most developers need to be
educated in the basics, just to be able to understand what the benefits are.

Regards,

Rick Morris

Tony wrote:

> Hi All,
>
> I've just been reading an article in PHP Architect magazine
> (http://www.phparch.com) which is the cover story for October called
> "Migrating from MySQL to PostgreSQL". I must say that this is a
> highly compelling article, especially for me, and is aimed at
> programmers that aren't necessarilly SQL experts or DBAs. For
> instance, like many PHP Web developers who use MySQL instead of flat
> files to store stuff! Instead of using a DB as a powerful tool. This
> article presents reasons as to why a more standards compliant DB is
> good for programmers, and why in some cases MySQL can be less of a
> friend to programmers than perhaps PostgreSQL.
>
> I honestly believe that if the advocates of PostgreSQL wrote an
> article or case study along the lines of this article, it would go a
> long way to attracting many more programmers. In my experience all of
> the articles and tutorials are written from the perspective of why PG
> is a better DB as a DB. Rather than emphasise aspects like "PG is
> great because you can move complicated code like this <insert
> complicated PHP/Perl code here> ..... normally dealt programatically
> to your DB which can be both faster and applied to any other
> programmers (VB, Java) that you are sharing the important enterprise
> data with. I've not seen anything in articles aimed at PHP/MySQL
> users saying, "Hey, look at how these triggers can make your life
> soooo much easier" or "Hey, look at how cascading can save you oh so
> much coding" or "Hey look at all this programmatical logic that can be
> put into queries just by writing your own functions"
>
> I have recently compared the PostgreSQL users to the Debian users
> (meant as a complement) by the fact that they are in general highly
> knowledgable of thier own subject and peripheral subjects too. They
> are passionate and well versed, and happy to nudge people in the
> direction of enlightenment without spoonfeeding them. But in the same
> way, the advocacy (IMHO) falls into the same boat as Debian. There is
> a certain self-assuredness that PostgreSQL is a far superior product
> and if someone can't see how obvious that is then maybe PG isn't for
> them (a little harsh I know but I'm trying to illustrate a point).
>
> My point is that there are thousands, tens of thousands of programmers
> out there, that need to know why and how PG is so great. My eyes have
> now been fully opened by this article, and got rid of my nagging
> feeling that there was something great about PG that I "Just wasn't
> grasping, and couldn't put my finger on". Maybe the advocacy team
> should be aiming for all those programmers that desperately need PG,
> but don't know it yet, and probably don't have time to garner enough
> DB experience to understand why they need it!
>
> Sadly the PHP Architect article is not free, I bought the electronic
> magazine for about $2, but believe it's worth every penny and more.
>
> Just my 2 cents.
>
> Apologies if the PG articles ARE out there and please notice that my
> comments do not say that they don't exist, but that I have never seen
> them.
>
> Cheers
>
> Tony.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if
> your
> joining column's datatypes do not match
>
>