pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Timestamp operator error
Date: Mon, 25 Feb 2002 21:03:39 -0800
Message-ID: <web-810156@davinci.ethosmedia.com> (raw)
In-Reply-To: <27308.1014698855@sss.pgh.pa.us>

Tom,

> Emergency fix?  This operator didn't behave reasonably in 7.1 either
> (at least not by my definition of reasonable).  What exactly would
> you have us do?

No, not you!  For me to fix.  You're a volunteer, as far as I'm
 involved.  I just wanted suggestions for a quick fix.  When I found
 the other issues, it was more reasonable to search-and-replace on
 values ("interval"() for interval() was easy).  I can't figure out how
 to pattern match on interval + timestamp, especially with variables
 involved.

Is there a way, for example, that I could disallow the TIMESTAMP -->
 DATE implicit conversion in my code?  That would break all the
 functions and views with this problem, and then I could identify them.

> Yah.  Offhand I'd argue that no information-discarding conversion
> should be implicitly invokable.  date->timestamp is fine;
> timestamp->date should require an explicit cast.  I've already
>  proposed
> that we add a flag to pg_proc to distinguish implicit from explicit
> conversion operations, and no one complained.  But we have not yet
> begun to argue about exactly which conversions should be allowed
> implicitly...

Hey, feel free to take up the argument here, too!  It is a SQL topic,
 after all ...

-Josh

______AGLIO DATABASE SOLUTIONS___________________________
                                       Josh Berkus
  Complete information technology      josh@agliodbs.com
   and data management solutions       (415) 565-7293
  for law firms, small businesses        fax 621-2533
    and non-profit organizations.      San Francisco



view thread (10+ messages)  latest in thread

Message-ID: <web-810156@davinci.ethosmedia.com>
Permalink:  ../web-810156@davinci.ethosmedia.com/
Also on:    postgresql.org/message-id/web-810156@davinci.ethosmedia.com

 · 

reply

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, tgl@sss.pgh.pa.us
  Subject: Re: Timestamp operator error
  In-Reply-To: <web-810156@davinci.ethosmedia.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