Re: sqlstate 02000 while declaring cursor/freeing statement - Mailing list pgsql-admin

From Thomas F. O'Connell
Subject Re: sqlstate 02000 while declaring cursor/freeing statement
Date
Msg-id 4DADE9CC-4B44-4A9A-A424-E7916937610C@sitening.com
Whole thread Raw
In response to sqlstate 02000 while declaring cursor/freeing statement  (andy rost <andy.rost@noaa.gov>)
Responses Re: sqlstate 02000 while declaring cursor/freeing statement  (Michael Fuhr <mike@fuhr.org>)
List pgsql-admin
On Aug 29, 2005, at 2:19 PM, andy rost wrote:

> I'm new to the PostgreSQL community so please pardon what is
> probably a silly question ...
>
> I'm in the process of porting Informix ESQL to PostgreSQL. I
> occasionally get sqlcode = 100 and sqlstate = 02000 when declaring
> cursors or freeing prepared statements. Is this normal? For example:
>
>     $declare loop1 cursor with hold for
>     select distinct ( tabname )
>     from meta ;
>
> results in sqlca.sqlcode = 100 and sqlca.sqlstate = '02000'

Andy,

According to the docs, a positive value of sqlcode indicates a
harmless condition:

http://www.postgresql.org/docs/8.0/static/ecpg-errors.html

The sqlstate of 02000 looks like the NO DATA code:

http://www.postgresql.org/docs/8.0/static/errcodes-appendix.html

I don't see anything wrong with your cursor declaration, so this just
looks like it's indicating that no rows were returned.

--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC

Strategic Open Source: Open Your i™

http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-469-5150
615-469-5151 (fax)

pgsql-admin by date:

Previous
From: jose fuenmayor
Date:
Subject: Re: size of indexes and tables (more than 1GB)
Next
From: Postgres Admin
Date:
Subject: plpgsql question