Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: "The Guardian" <theguardian@vsnl.net>, <pgsql-sql@postgresql.org>
Subject: Re: Problems to be solved as soon as possible
Date: Mon, 29 Sep 2003 12:20:20 -0700
User-Agent: KMail/1.4.3
References: <EBEDKBEGBLEDODHNFHBLMEFOCAAA.theguardian@vsnl.net>
In-Reply-To: <EBEDKBEGBLEDODHNFHBLMEFOCAAA.theguardian@vsnl.net>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200309291220.20508.josh@agliodbs.com>

"The Guardian",

> Dear Support Team,

We are not a "support team".  We are your fellow PostgreSQL users, and are=
=20
helping you out of our personal generosity and desire to promote Postgres=
=20
use.   Nobody on this list is paid to answer your question.

You are expected to "pay" for this support by, in turn, helping other users=
=20
who are less experienced than you.   This peer-to-peer help strategy has ke=
pt=20
PostgreSQL going for 16 years, and is often faster than traditional=20
commercial support.   However, you should remember that the people you are=
=20
talking to are not paid support staff, and remember that the people answeri=
ng=20
your questions are doing you a favor.

> 	We are hosting a website which was originally designed in some version of
> Debian Linux and having PostgreSQL as back end. The developers have made a
> script which creates several tables in the database. Some of the tables h=
ave
> datatypes like DateTime. When i run those scripts in PostgreSQL of Red hat
> Linux 7.2, they run perfectly. But when i run the same scrips in PostgreS=
QL
> of Redhat Linux 9.0, it displays an error message of "data type DATETIME =
not
> found."

	The DATETIME data type was included in PostgreSQL versions 6.5 to 7.1 (as =
I=20
recall) in order to provide compatibility with certain commercial database=
=20
products.  Before 7.2, the core developers decided that it was silly to=20
maintain support for a data type which was not SQL-standard just for=20
compatibility with 2 commercial databases, and so support for DATETIME was=
=20
phased out over the next two versions.

	You can fix your scripts by doing a search-and-replace on DATETIME and=20
replacing it with TIMESTAMP, which provides the same functionality.

--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco