RPK wrote:
> PGSQL and NPGSQL does not display exact error while using with VB.NET. We
> faced a lot of trouble to find out actually where an error occured.
>
> For example in a routine we need to insert a record to the table. I forgot
> to use "values" clause in the Insert Query, but PGSQL displayed error "No
> source code available" in the routine where we opened the connection.
> Whereas, Oracle displayed exact error that "Invalid Insert statement".
>
> There are many such situation where we remained puzzled and later found
> error somewhere else.
You should make sure and check the postgresql logs at all times. They
are the definitive source for anything you are trying to do. If
PostgreSQL doesn't report an error, you know the problem is in your code.
Joshua D. Drake
>
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/