RE: current is broken

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: current is broken
Date: 2000-09-13 05:31:51
Message-ID: 000e01c01d43$eb6a4b00$2801007e@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Tom Lane
>
> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> >> Ooops. I guess libpq needs to supply a copy of this function?
>
> > Simply copying the function won't work since the way to know what
> > encoding is used for this session is different between backend and
> > frontend.
>
> 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 ?

Regards.

Hiroshi Inoue

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Warner 2000-09-13 05:44:25 Re: current is broken
Previous Message Tom Lane 2000-09-13 05:02:51 Re: current is broken