Error: relation does not exist

Re: Error: relation does not exist

--0__=0ABBFB2CDFF06E768f9e8a93df938690918c0ABBFB2CDFF06E76
Content-type: multipart/alternative;
Boundary="1__=0ABBFB2CDFF06E768f9e8a93df938690918c0ABBFB2CDF F06E76"

--1__=0ABBFB2CDFF06E768f9e8a93df938690918c0ABBFB2CDFF06E76
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: quoted-printable


You seem to have console access to your PG database. If I had a mysterious
Relation does not exist
I would turn on statement logging. It is a switch in postgresql.conf.
Uncomment log_statement =3D 'mod'.
I believe you have to restart PG to apply it. The switch is documented in
the Postgresql 8.0 documentation.
And you need to have logging turned on. I did not see if you said the
PostgreSQL server was Linux or Windows.
You will not want to leave log_statement on for very long.

Other logging option include ODBC tracing, and the PostgreSQL ODBC driver's
option for MyLog.
Some of this should tell you if the problem is IN the pgodbc driver, or in
how your applications statements are interacting with your PostgreSQL
database.





Greg Campbell ENG-ASE/Michelin US5
Lexington, South Carolina
803-951-5561, x75561
Fax: 803-951-5531
greg.campbell@us.michelin.com



=
=20
"Rohit Prakash =
=20
Khare" =
=20
=20
indiatimes.com> =
=20
cc=
=20
08/03/2006 13:34 =
=20
Subject=
=20
Re: Re: [ODBC] Error: relation does=
=20
Please respond to not exist =
=20
"Rohit Prakash =
=20
Khare" =20
sh123@indiatimes. =
=20
com> =
=20
=
=20
=
=20




Greg,


I tried many times and checked all the syntax. I even created a new table
having no relation with other tables. I always use lower case SQL. Not
following why it is happening.



greg.campbell@us.michelin.com wrote:


Are the statements you pass using correct case and delimiters.

PostgreSQL will fold
"SELECT EMPLOYEES. NAME FROM EMPLOYEES"
into lower case e.g.
"SELECT employees.name FROM employees"
which produces the error if there is no "employees" table (the
table/relation is name EMPLOYEES or Employees).
The correction is to delimit the object names "SELECT 'EMPLOYEES'.'NAME'
FROM .'EMPLOYEES'". Notice the single quotes.
Of course most long time PostgreSQL users name all objects in lowercase to
avoid all the case folding/delimiting business.

Greg Campbell ENG-ASE/Michelin US5
Lexington, South Carolina
803-951-5561, x75561
Fax: 803-951-5531
greg.campbell@us.michelin.com

Inactive hide details for "Rohit Prakash Khare" ndiatimes.com>"Rohit Prakash Khare"

=
=20
"Rohit Prakash =
=20
Khare" =
=20
=20
indiatimes.com> =
=20
Sent by: To=
=20
pgsql-odbc-owner@ =
=20
postgresql.org =20
gresql.org> =
=20
=
=20
08/03/2006 12:38 cc=
=20
=
=20
=
=20
Please respond to Subject=
=20
"Rohit Prakash =
=20
Khare" [ODBC] Error: =
=20
relation does =
=20
not exist =
=20
=
=20
=
=20
=
=20
=
=20
=
=20
=
=20



Whenever I create a New Table using GUI PGAdmin III, and then call the
table from VB.NET 2003 using ODBC Connection, it displays an error:
"Relation does not exist".

But when I create a Table from command line console of PGSQL, then I have
no problems. Everything works fine. What is the problem.

...
RPK

Sign Up for your FREE eWallet at www.wallet365.comSign Up for your FREE
eWallet at www.wallet365.com


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

--1__=0ABBFB2CDFF06E768f9e8a93df938690918c0ABBFB2CDFF06E76
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
Content-transfer-encoding: quoted-printable

You seem to have console access to your PG database. If=
I had a mysterious Relation does not exist

I would turn on statement logging. It is a switch in postg=
resql.conf. Uncomment log_statement =3D 'mod'.

I believe you have to restart PG to apply it. The switch =
is documented in the Postgresql 8.0 documentation.

And you need to have logging turned on. I did not see if y=
ou said the PostgreSQL server was Linux or Windows.

You will not want to leave log_statement on for very long.=




Other logging option include ODBC tracing, and the Postgre=
SQL ODBC driver's option for MyLog.

Some of this should tell you if the problem is IN the pgod=
bc driver, or in how your applications statements are interacting with yo=
ur PostgreSQL database.











Greg Campbell ENG-ASE/Michelin US5

Lexington, South Carolina

803-951-5561, x75561

Fax: 803-951-5531

greg.campbell@us.michelin.com



6" height=3D"16" alt=3D"Inactive hide details for "Rohit Prakash Khare=
" <rohitprakash123@indiatimes.com>">"Rohit=
Prakash Khare" <rohitprakash123@indiatimes.com>

06E768f9e8a93df9@michelin.com); background-repeat: no-repeat; " width=3D"40= %"> "Rohit Prakash Khare" <rohitprakash123= @indiatimes.com> 08/03/2006 13:34 er">Please respond to "Rohit Prakash Khare"<rohitprakash123@indiatimes.com> >

<= /tr> 8f9e8a93df9@michelin.com" border=3D"0" height=3D"1" width=3D"58" alt=3D""><= br> To "> =3D"0" height=3D"1" width=3D"1" alt=3D""> <greg.campbell@us.michelin.com> 8f9e8a93df9@michelin.com" border=3D"0" height=3D"1" width=3D"58" alt=3D""><= br> cc "> =3D"0" height=3D"1" width=3D"1" alt=3D""> 8f9e8a93df9@michelin.com" border=3D"0" height=3D"1" width=3D"58" alt=3D""><= br> Subject "100%"> der=3D"0" height=3D"1" width=3D"1" alt=3D""> Re: Re: [ODBC] Error: relation does not exist 8f9e8a93df9@michelin.com" border=3D"0" height=3D"1" width=3D"1" alt=3D""> td> helin.com" border=3D"0" height=3D"1" width=3D"1" alt=3D"">

I tried many times and checked all the syntax. I even created a new tabl=
e having no relation with other tables. I always use lower case SQL. Not fo=
llowing why it is happening.

greg.campbell@us.michelin.com wrote:=20

Are the statements you pass using correct case and deli=
miters.



PostgreSQL will fold

"SELECT EMPLOYEES. NAME FROM EMPLOYEES"

into lower case e.g.

"SELECT employees.name FROM employees"

which produces the error if there is no "employees" table (the ta=
ble/relation is name EMPLOYEES or Employees).

The correction is to delimit the object names "SELECT 'EMPLOYEES'.'NAM=
E' FROM .'EMPLOYEES'". Notice the single quotes.

Of course most long time PostgreSQL users name all objects in lowercase to =
avoid all the case folding/delimiting business.



Greg Campbell ENG-ASE/Michelin US5

Lexington, South Carolina

803-951-5561, x75561

Fax: 803-951-5531

greg.campbell@us.michelin.com



"Rohit Prakash Khare" <rohitprakash123@indiat=
imes.com>

"Rohit Prakash Khare" <rohitprakash123= @indiatimes.com> Sent by: pgsql-odbc-owner@postgresql.org=20 08/03/2006 12:38 ter">Please respond to "Rohit Prakash Khare"<rohitprakash123@indiatimes.com> >

= To <pgsql-odbc@postgresql.org> = cc 768f9e8a93df9@michelin.com" border=3D"0" height=3D"1" width=3D"1" alt=3D"">= = Subject [ODBC] Error: relation does not exist 68f9e8a93df9@michelin.com" border=3D"0" height=3D"1" width=3D"1" alt=3D""><= /td> chelin.com" border=3D"0" height=3D"1" width=3D"1" alt=3D"">