| From: | Perry Smith <pedz(at)easesoftware(dot)com> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ***SPAM*** Re: With Recursive / Recursive View question |
| Date: | 2022-08-21 02:02:41 |
| Message-ID: | 3E66E12E-DE90-4931-8D71-0CA0B21CD68A@easesoftware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Aug 20, 2022, at 19:38, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
>
>
>> On Aug 20, 2022, at 15:42, Perry Smith <pedz(at)easesoftware(dot)com> wrote:
>>
>> To rephrase, is it possible to write a view that would work from the child terms out towards the ancestors?
>
> Assuming that the concern is that you want to parameterize this predicate:
>
> WHERE basename = '10732.emlx'
>
> ... you might consider an SQL function taking basename as a parameter.
Yea. If I did a function, I would just pass in the id. I’ve used functions only rarely. For whatever reason, I’ve always been very skittish around them. But perhaps I need to grow up.
Thank you again,
Perry
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Perry Smith | 2022-08-21 02:48:55 | Re: ***SPAM*** Re: With Recursive / Recursive View question |
| Previous Message | Christophe Pettus | 2022-08-21 00:38:04 | Re: With Recursive / Recursive View question |