Thread: editors with colum positioning for debugging?
Hi I am doing my work in windows attached to a postgres server on linux fedora core3. I have been using pgadminIII and amd am trying the demo of EMS. My question is I dont see an easy way to find an error. Typical error text is syntax error at or near "trans" at character 825 But determining character 825 is a little slow by hand. Any of you guru's have some ideas you use (I am sure you dont get the number of errors I am). By the way my issues were caused by SELinux not being turned off, I turned it off and re-did my postgres rpm and all is well (no pg_user error). I was also able to add the view that had given me the row too large error. Joel Fradkin Wazagua, Inc. 2520 Trailmate Dr Sarasota, Florida 34243 Tel. 941-753-7111 ext 305 jfradkin@wazagua.com www.wazagua.com Powered by Wazagua Providing you with the latest Web-based technology & advanced tools. © 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc This email message is for the use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and delete and destroy all copies of the original message, including attachments.
"Joel Fradkin" <jfradkin@wazagua.com> writes:
> My question is I don�t see an easy way to find an error.
> Typical error text is syntax error at or near "trans" at character 825
> But determining character 825 is a little slow by hand.
PG 8.0 produces more useful output. A trivial example:
regression=# select
regression-# 1/0 as a,
regression-# 1/ as b,
regression-# 1/2 as c;
ERROR: syntax error at or near "as" at character 27
LINE 3: 1/ as b, ^
regression=#
regards, tom lane
Very cool (I tried to get 8 on fedora, but think I was missing it somehow.).
I also noticed if I run in EMS (course I need to buy it)it positions me on
the error if I am in the editor not the builder.
I am a little afraid of using 8 as it is brand new, and this will be on a
production machine. I could use 8 for development and 7 for production I
guess.
Joel Fradkin
Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel. 941-753-7111 ext 305
jfradkin@wazagua.com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
C 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, IncThis email message is for the use of the intended recipient(s)
andmay
contain confidential and privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and delete and destroy
all copies of the original message, including attachments.
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Saturday, January 22, 2005 5:21 PM
To: Joel Fradkin
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] editors with colum positioning for debugging?
"Joel Fradkin" <jfradkin@wazagua.com> writes:
> My question is I don't see an easy way to find an error.
> Typical error text is syntax error at or near "trans" at character 825
> But determining character 825 is a little slow by hand.
PG 8.0 produces more useful output. A trivial example:
regression=# select
regression-# 1/0 as a,
regression-# 1/ as b,
regression-# 1/2 as c;
ERROR: syntax error at or near "as" at character 27
LINE 3: 1/ as b, ^
regression=#
regards, tom lane
On Jan 22, 2005, at 5:12 PM, Joel Fradkin wrote: > My question is I don’t see an easy way to find an error. > Typical error text is syntax error at or near "trans" at character 825 > > But determining character 825 is a little slow by hand. In pgEdit you can use the "Goto Point" command to jump to a specific offset in the file. I hope to have something better in the near future to automatically move the cursor for you when an error is detected. John DeSoi, Ph.D. http://pgedit.com/ Power Tools for PostgreSQL