From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | walther(at)technowledgy(dot)de, Steve Chavez <steve(at)supabase(dot)io>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql: add \create_function command |
Date: | 2024-01-26 20:13:39 |
Message-ID: | CAFj8pRDZsiAx+U3h8EUp=HUQrBhWDPcvW_5MmWstDqeu_4TjOg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
pá 26. 1. 2024 v 21:04 odesílatel Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> napsal:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> > but why you need to do in psql? - you can prepare content outside and
> > execute just like echo "CREATE FUNCTION ...." | psql
>
> The bit that's probably hard if you're trying to do this in a shell
> script is "quote this data as a SQL string literal". psql can get
> that right even in the face of encoding considerations,
> standard_conforming_strings, etc. Not sure you can build a
> fully bulletproof solution outside.
>
I don't know, maybe I have a problem with the described use case. I cannot
imagine holding the body and head of PL routines in different places and I
don't understand the necessity to join it.
On second hand, few years ago (if I remember well, I proposed some like
`:{file}`. I don't remember the syntax. But it was not finished, and then I
wrote
https://github.com/okbob/pgimportdoc
The possibility for some simple import external data can be nice
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-01-26 20:17:46 | Re: psql: add \create_function command |
Previous Message | Tom Lane | 2024-01-26 20:04:55 | Re: psql: add \create_function command |