From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Bart Degryse <Bart(dot)Degryse(at)indicator(dot)be> |
Cc: | PostgreSQL SQL List <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Function description |
Date: | 2008-02-15 11:17:55 |
Message-ID: | 47B574E3.9070401@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Bart Degryse wrote:
>>>>> Richard Huxton <dev(at)archonet(dot)com> 2008-02-15 11:50 >>>
>>>> To see how e.g. \dC etc work start psql with -E
>>>>
>>> I'm sorry, but I don't have commandline access to the database. That would
>>> require an amount of trust and a level of competence our ICT department is incapable of.
>> Well, if you have access to prt 5432 (or whatever you are using) on the
>> DB host you can run psql locally: psql -h <db-hostname>
>
> All I have is my desktop Windows pc. I work on the database using EMS SQL Manager for PostgreSQL.
> There I can run whatever statement I want, but it's not psql.
> What do you exactly mean with "run psql locally"? Should I be able to run some psql.exe
> from my windows cmd environment. Or should I start something else first?
Well, the windows installer comes with the backend database server,
psql.exe, pgadmin, manuals etc. - I don't know if you can just install
psql. From psql you can access local or remote databases. Same for the
pg_dump/restore command-line tools. Unless EMS is accessing the server
via ODBC or similar it should just work.
>> As a last resort you can always see how they work on a local copy, then
>> cut + paste the SQL.
> Here too, I don't know what you mean exactly with "a local copy".
Install PostgreSQL locally, copy the schema from your main server and
add some test data.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Jyoti Seth | 2008-02-15 11:46:27 | Packages |
Previous Message | Bart Degryse | 2008-02-15 11:05:39 | Re: Function description |