In my opinion, the use of such a feature is to make simple, commonly
used scripts available from wherever you start up psql and no matter
what database you are connecting to. On Oracle/SQL*Plus I have used
this feature to create simple scripts that replicate informational
backslash commands in psql. If there was someway to define your own
backslash commands in the .psqlrc, that would be even better.
Miles.
On Fri, Sep 6, 2013 at 11:58 AM, David Kerr <dmk@xxxxxxxxxxxxxx> wrote:
> On Fri, Sep 06, 2013 at 10:45:26AM -0700, David Johnston wrote:
> - lup wrote
> - >>
> - >>
> - > I wonder if this would at least get the full path on-screen for a c/p
> - > \! for d in $SQLPATH; do find $d -name
> - > <script-filename>
> - > ; done
> - >
> - > That said, I would down-vote this suggestion. I tend to put sql files
> - > in amongst my various project dirs and maintaining the envvar isn't
> - > worth it.
> - >
> - > Anything I re-use I make into a function.
> -
> - Usually a down-vote there is something that can go wrong if the feature is
> - implemented. Simply not personally having a use for said feature normally
> - results in a "+0" vote or something similar.
> -
> - The big issue with environment variables is their ability to have resolution
> - conflicts. I think the general idea has merit though setting symbolic-links
> - (in Linux variants at least) can get you some of the way there in a less
> - error-prone (but more verbose) way.
> -
> - Ultimately feature requests get made to here then end up on the ToDo listing
> - if the idea has traction.
> -
> - David J.
>
> I suspect this feature makes more sense on a windows platform. On linux where we can
> go psql -f ${SQLPATH}/file.sql . it becomes less pressing. Even Oracle
> on unix/linux where you can go sqlplus <<EOD @${SQLPATH}/file.sql EOD. makes
> it less a requirement.
>
> on the other hand, does seems like a pretty easy thing to implement.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
