On 13.Jan.2003 -- 12:26 PM, Sarah Windler wrote:
> Thank you for the hint. I am trying to understand, what you mean:
>
> 1.Setup the database connection --> setup error
> 2. Setup a prepStatement (con.prepareStatement(queryString) --> ???
> 3. exeute the query: prepStmt.execute()] --> r
Thank you for the hint. I am trying to understand, what you mean:
1.Setup the database connection --> setup error
2. Setup a prepStatement (con.prepareStatement(queryString) --> ???
3. exeute the query: prepStmt.execute()] --> runtime error
Is the second a runtime or setup error?
regar
On 13.Jan.2003 -- 10:57 AM, Windler Burri, Sarah wrote:
> Hi
> Thank you for your reply, but I am not agree:
> 1. Both errors in the example are runtime errors! Or more precisaly: Who
> decides, which error ist a syntax or runtime error?
The try{ block starts just before prepareCall() or prepare
Message-
From: Christian Haul [mailto:[EMAIL PROTECTED]]
Sent: Montag, 13. Januar 2003 10:38
To: [EMAIL PROTECTED]
Subject: Re: sql errors and esql
On 13.Jan.2003 -- 09:47 AM, Sarah Windler wrote:
> Hi
> I don't understand, why some sql errors goes through the
> esql:error-re
On 13.Jan.2003 -- 09:47 AM, Sarah Windler wrote:
> Hi
> I don't understand, why some sql errors goes through the
> esql:error-results pipe and others not.
> For example:
> 1. SQL> select mgmt_ip_addressm from v_ps_port_traffic;
> select mgmt_ip_addressm from v_ps_port_traffic
>*
> ERROR a
Hi
I don't understand, why some sql errors goes through the
esql:error-results pipe and others not.
For example:
1. SQL> select mgmt_ip_addressm from v_ps_port_traffic;
select mgmt_ip_addressm from v_ps_port_traffic
*
ERROR at line 1:
ORA-00904: "MGMT_IP_ADDRESSM": invalid identifier
2.SQ
