On Wed, May 9, 2018 at 3:05 AM, Pavel Stehule <pavel.steh...@gmail.com> wrote:
> > > 2018-05-09 9:59 GMT+02:00 John McKown <john.archie.mck...@gmail.com>: > >> I just wanted to throw this out to the users before I made a complete >> fool of myself by formally requesting it. But I would like what I hope >> would be a minor change (enhancement) to the psql command. If you look on >> this page, https://wiki.postgresql.org/wiki/Shared_Database_Hosting , >> you will see a number of example which look like: >> >> psql -U postgres template1 -f - << EOT >> >> REVOKE ALL ON DATABASE template1 FROM public; >> REVOKE ALL ON SCHEMA public FROM public; >> GRANT ALL ON SCHEMA public TO postgres; >> CREATE LANGUAGE plpgsql; >> >> EOT >> >> >> To me this looks similar to a UNIX shell script. Now, going sideways for >> a second, if someone wanted to create a "self contained" awk script. It >> would look something like: >> >> #!/bin/awk -f >> ... awk code ... >> >> When a user executes the above from the command line, the UNIX system >> runs the program in the first "magic" line as if the user had entered >> "/bin/awk -f ..." where the ... is replaced by the name of the file >> executed followed by the rest of the command line parameters. >> >> I think it would be nice if psql would do the same, mainly for >> "consistency" with other UNIX scripting languages, such as python, perl, & >> gawk. >> > > These languages has defined # as line comment. It is not true for SQL. > Thanks, that looks like a "NO" vote to me. > > Regards > > Pavel > > -- We all have skeletons in our closet. Mine are so old, they have osteoporosis. Maranatha! <>< John McKown
