pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Diehl, Jeffrey <jdiehl@sandia.gov>
To: pgsql-sql@postgresql.org
Subject: Re: Issues w/ 7.1 to 7.2 upgrade.
Date: Tue, 19 Feb 2002 19:38:03 -0800
Message-ID: <web-698098@davinci.ethosmedia.com> (raw)
In-Reply-To: <B51F0C636E578A4E832D3958690CD73E0130C20A@es04snlnt>

Mike,

> I just upgraded from 7.1 to 7.2, mainly because of the facts that
>  vacuum
> doesn't do table locks and I thought that "replace into" would be in
>  7.2.
> 
> Anyway, I don't see that "replace into" is there...

Nope.  I hadn't had the impression from the list traffic that the
 developers ever considered letting in this bit of non-standard SQL.
  While it's undoubtedly useful, it's not in the SQL 92 spec and a
 *lot* of extra programming would be required to support it (for
 example, those of us who use UPDATE and INSERT triggers might find
 ourselves re-writing them all).

Remember:  If you really, really want "replace into", Postgres *is* an
 open-source database.  You are always welcome to hack your own
 "replace into" patch.

> Also, I noticed a slight difference that caught me off guard:
> 
> If I try to insert '1234567890' into a varchar(5) under 7.1, the
>  value of
> the field will be '12345'.
> 
> If I try it under 7.2, I get an error.

Another annoying change per the spec, I believe.  Personally, this
 change made me happy because unexpected truncations had previously
 escaped my notice.  But it did lead to a spate of emergency bug fixes
 in my code.

-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 (3+ messages)  latest in thread

Message-ID: <web-698098@davinci.ethosmedia.com>
Permalink:  ../web-698098@davinci.ethosmedia.com/
Also on:    postgresql.org/message-id/web-698098@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, jdiehl@sandia.gov
  Subject: Re: Issues w/ 7.1 to 7.2 upgrade.
  In-Reply-To: <web-698098@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