From: Kevin Brown <kevin@sysexperts.com>
To: pgsql-hackers@postgresql.org
Subject: Re: Are we losing momentum?
Date: Tue, 15 Apr 2003 02:10:42 -0700
Message-ID: <20030415091042.GA1833@filer> (raw)
In-Reply-To: <5758.1050388837@sss.pgh.pa.us>
References: <200304142237.h3EMbvv13720@candle.pha.pa.us>
<2703.1050364467@sss.pgh.pa.us>
<20030415015217.GA96608@rcfile.org>
<Pine.NEB.4.51.0304151132210.385@angelic-vtfw.cvpn.cynic.net>
<5758.1050388837@sss.pgh.pa.us>
Tom Lane wrote:
> Curt Sampson <cjs@cynic.net> writes:
> > That's a pretty reasonable thought. I work for a shop that sells
> > Postgres support, and even we install MySQL for the Q&D ticket tracking
> > system we recommend because we can't justify the cost to port it to
> > postgres. If the postgres support were there, we would surely be using it.
>
> > How to fix such a situation, I'm not sure. "MySQL Compatability Mode,"
> > anyone? :-)
>
> What issues are creating a compatibility problem for you?
Erm...reserved words? "Freeze" is a reserved word, for instance, and
that actually bit me when converting an MS-SQL database...
I have no problem with reserved words in principle, at least when they
refer to the SQL-standard commands and their options, but it's not
clear that turning options (such as FREEZE) for PG-specific commands
(such as VACUUM) into reserved words is a good idea. But it may not
be possible to avoid it, unfortunately. :-(
--
Kevin Brown kevin@sysexperts.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: kevin@sysexperts.com
Subject: Re: Are we losing momentum?
In-Reply-To: <20030415091042.GA1833@filer>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox