RE: current is broken

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: Inoue(at)tpf(dot)co(dot)jp
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org
Subject: RE: current is broken
Date: 2000-09-13 10:41:36
Message-ID: 20000913194136N.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > Good point --- in fact, the encoding itself might be different between
> > the backend and frontend. That seems to imply that "truncate to
> > NAMEDATALEN bytes" could yield different results in the frontend than
> > what the backend would get.
> >
> > > Even better idea would be creating a new function that returns the
> > > actual rule name (after being shorten) from given view name. I don't
> > > think it's a good idea to have codes to get an actual rule name in two
> > > separate places.
> >
> > Given the above point about encoding differences, I think we *must*
> > do the truncation in the backend ...
> >
>
> I agree with Tatsuo.
> However we already have relkind for views.
> Why must we rely on rulename to implement isViewRule()
> in the first place ?

Oh, I forgot about that.

BTW, does anybody know about the status of pg_dump? It seems tons of
features have been added, but I wonder if all of them are going to
appear in 7.1. Especially now it seems to have an ability to dump
Blobs, but the flag (-b) to enable the feature has been disabled. Why?
--
Tatsuo Ishii

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Denis Perchine 2000-09-13 11:07:56 Fwd: Problems inserting data
Previous Message Tatsuo Ishii 2000-09-13 10:41:04 Re: PL/pgSQL does not accept none ASCII identifiers