From: | SunWuKung <Balazs(dot)Klein(at)axelero(dot)hu> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: regarding debugging? |
Date: | 2006-02-03 20:27:45 |
Message-ID: | MPG.1e4ddb296e3fdb9f98968c@news.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
In article <C00437CF(dot)3F9D0%scott_ribe(at)killerbytes(dot)com>,
scott_ribe(at)killerbytes(dot)com says...
> > where we can check the execution of our program or we can dry run our code, is
> > there aby option or feature with PGSQL for the same purpose that we can check
> > our PGSQL statements?
>
> No, unfortunately not. What I do is:
>
> - error check everything you can, and use RAISE EXCEPTION with descriptive
> error messages
>
> - come up with test cases to exercise all branches of code
>
> - print useful debugging info while tracking down problems
>
>
>
EMS Postgresql Manager has a debugger in it. Its not perfect but still
it is quite useful.
B.
From | Date | Subject | |
---|---|---|---|
Next Message | Rikard Pavelic | 2006-02-03 20:38:58 | grouping of functions |
Previous Message | Uwe C. Schroeder | 2006-02-03 20:14:04 | Re: PgSQL as part of commercial product |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-02-05 00:58:52 | Re: UnixODBC-2.2.8-2.3.0 driver |
Previous Message | Niklas Johansson | 2006-02-03 13:20:31 | Re: Help writing a piece of SQL |