Re: Heres a good one...

From: Steve Meynell <steve(at)candata(dot)com>
To: Anuradha Ratnaweera <anuradha(at)gnu(dot)org>
Cc: Postgresql Mailing List <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Heres a good one...
Date: 2001-04-30 15:15:20
Message-ID: 3AED8187.F17D6E61@candata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

First, thank you very much for trying but you were a bit off the mark but
close. Second, posting_date being of type char(4) is quite legal and
irrelevant for this exercise but for argument sake lets say char(15) but
apart from all that...

Your sql statement was close but it only update 4 out of the possible 6 that
is should have updated... journal.objectid# 103 should have been updated
because of journal.objectid# 100 was and journal.objectid# 106 should have
been because it alone met the before March 31 and update flag = H criteria.
But it is a start for me thanks.

And your second sql statement just didn't work. It said 'ERROR: parser:
parse error at or near "select"'

Steve

Anuradha Ratnaweera wrote:

> First, posting_date in journal can _NOT_ be of type char(4)! I guess it is
> a "date".
>
> Try
>
> update journal set gl_update_flag='Y' from distrib where
> journal.gl_update_flag = 'H' and journal.posting_date <= '2001-03-31' and
> (journal.objectid = distrib.distrib_objectid or journal.objectid =
> distrib.source_objectid)
>
> or
>
> update journal set gl_update_flag='Y' where gl_update_flag = 'H' and
> posting_date <= '2001-03-31' and ((objectid in select distrib_objectid
> from distrib) or (objectid in select source_objectid from distrib))
>

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2001-04-30 15:28:37 Re: SQL Server -> Postgres migration: Stored Procedure replacement?
Previous Message Martín Marqués 2001-04-30 09:25:39 views and rules on update