From: Josh Berkus <josh@agliodbs.com>
To: The Guardian <theguardian@vsnl.net>
To: pgsql-sql@postgresql.org
Subject: Re: Problems to be solved as soon as possible
Date: Mon, 29 Sep 2003 12:20:20 -0700
Message-ID: <200309291220.20508.josh@agliodbs.com> (raw)
In-Reply-To: <EBEDKBEGBLEDODHNFHBLMEFOCAAA.theguardian@vsnl.net>
References: <EBEDKBEGBLEDODHNFHBLMEFOCAAA.theguardian@vsnl.net>
"The Guardian",
> Dear Support Team,
We are not a "support team". We are your fellow PostgreSQL users, and are
helping you out of our personal generosity and desire to promote Postgres
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
who are less experienced than you. This peer-to-peer help strategy has kept
PostgreSQL going for 16 years, and is often faster than traditional
commercial support. However, you should remember that the people you are
talking to are not paid support staff, and remember that the people answering
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 have
> 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 PostgreSQL
> 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
recall) in order to provide compatibility with certain commercial database
products. Before 7.2, the core developers decided that it was silly to
maintain support for a data type which was not SQL-standard just for
compatibility with 2 commercial databases, and so support for DATETIME was
phased out over the next two versions.
You can fix your scripts by doing a search-and-replace on DATETIME and
replacing it with TIMESTAMP, which provides the same functionality.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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-sql@postgresql.org
Cc: josh@agliodbs.com, theguardian@vsnl.net
Subject: Re: Problems to be solved as soon as possible
In-Reply-To: <200309291220.20508.josh@agliodbs.com>
* 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