| From: | "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net> |
|---|---|
| To: | Kenneth Gonsalves <lawgon(at)thenilgiris(dot)com> |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, talexb(at)gmail(dot)com, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: parse error at or near "(" -- Huh??? |
| Date: | 2004-12-13 08:44:11 |
| Message-ID: | 20041213034411.76e3f470.darcy@druid.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Mon, 13 Dec 2004 09:27:04 +0530
Kenneth Gonsalves <lawgon(at)thenilgiris(dot)com> wrote:
> and while on this topic, how does one interpret the line numbers one
> gets when running psql -f to create tables?
Forget about line numbers. Add the -e option and your statements will
show up in your output. Here is a sample (Unix) command line that I
commonly use to run statements from a file:
psql table -f in.file -e > out.file 2>&1
Now I can search the file for "ERROR" and see exactly what preceded it.
--
D'Arcy J.M. Cain <darcy(at)druid(dot)net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schaber | 2004-12-13 10:25:17 | Hide schemas and tables |
| Previous Message | Kenneth Gonsalves | 2004-12-13 03:57:04 | Re: parse error at or near "(" -- Huh??? |