Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f47H4rA88862 for ; Mon, 7 May 2001 13:04:53 -0400 (EDT) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.10.1/8.10.1) id f47H4jJ13963; Mon, 7 May 2001 13:04:45 -0400 (EDT) From: Bruce Momjian Message-Id: <200105071704.f47H4jJ13963@candle.pha.pa.us> Subject: Re: Dateadd In-Reply-To: <27100.989125217@sss.pgh.pa.us> "from Tom Lane at May 6, 2001 01:00:17 am" To: Tom Lane Date: Mon, 7 May 2001 13:04:45 -0400 (EDT) CC: Josh Berkus , pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL90 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200105/48 X-Sequence-Number: 2849 > There was some talk recently of putting together packages of function > and operator definitions to ease portability from other DBMSes to PG. > I'd have no objection to including "+ as string concatenation" in a > set of operators that're clearly marked as MS-SQL-isms. But I don't > think we'd do the world any favor by adopting a clearly nonstandard > notation as part of our standard operator set. Now that someone else thinks this is a good idea, I have added to the TODO list: * Allow plug-in modules to emulate features from other databases -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026