cvs postgresql current lacks 'ksqo' ? odbc/pgadmin does not work 
Author Message
 cvs postgresql current lacks 'ksqo' ? odbc/pgadmin does not work

Hi,

I've checked out and build current developement postgresql
from cvs.
The server runs fine beside a simple bug in the conversion
testing (seems to be a bug in the test)

Now I'm unable to connect with either PGAdmin2 1.2
nor PGAdmin2 1.3.60 to the database - it returns an
unspecified error message.
I was able to track it down to the fact, that pgodbc
which in turn is used by pgadmin, sets some compatibility
parameters per default, such as "set ksqo to 'ON'"
which happens to gone away with postgresql-current.

Since I like to try some things out I would be happy with
a quick dirty patch, but neither the pgodbc source compiles
nor do I find the relevant parts to the option setting in
the postgres-sources so I could at least get it to a
"dummy-accept"

Does anybody has an idea for me?

Btw, what happend to the ksqo anyways?

Best regards
Tino

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command



Sun, 30 Jan 2005 23:21:31 GMT
 cvs postgresql current lacks 'ksqo' ? odbc/pgadmin does not work

Quote:

> Now I'm unable to connect with either PGAdmin2 1.2
> nor PGAdmin2 1.3.60 to the database - it returns an
> unspecified error message.
> I was able to track it down to the fact, that pgodbc
> which in turn is used by pgadmin, sets some compatibility
> parameters per default, such as "set ksqo to 'ON'"
> which happens to gone away with postgresql-current.

My vague recollection is that this is fixed in the development version
of the ODBC driver, but someone from the ODBC camp should probably
confirm that...

Quote:
> Btw, what happend to the ksqo anyways?

KSQO hasn't actually worked since PostgreSQL 7.0, and was a bad idea
in the first place, IMHO. It has been put out of its misery in the
development sources.

Cheers,

Neil

--

PGP Key ID: DB3C29FC

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org



Sun, 30 Jan 2005 23:57:27 GMT
 cvs postgresql current lacks 'ksqo' ? odbc/pgadmin does not work

Quote:

> Since I like to try some things out I would be happy with
> a quick dirty patch, but neither the pgodbc source compiles
> nor do I find the relevant parts to the option setting in
> the postgres-sources so I could at least get it to a
> "dummy-accept"

Can't help you with pgodbc, but if you want "set ksqo" to be
accepted, add a dummy variable in src/backend/utils/misc/guc.c
(look at the entry for geqo for a model).

Quote:
> Btw, what happend to the ksqo anyways?

It's been dead for several releases and showed no sign of ever getting
fixed, so Bruce decided to take it out.

Breaking older odbc drivers might be a sufficient reason to leave a
dummy SET variable in there awhile longer, though.  Not sure.  The
schema changes in 7.3 might mean that using an old driver would be a
bad idea anyway.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate

message can get through to the mailing list cleanly



Mon, 31 Jan 2005 00:42:07 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. cvs postgresql current lacks 'ksqo' ? odbc/pgadmin

2. cvs postgresql current lacks 'ksqo' ? odbc/pgadmin does

3. It's not ODBC - It's not ASP - It's OLE/DB

4. VC5.0's ODBC is not compatible with VC4.2's ODBC

5. 'LIKE' does not work in VB

6. OPENXML - rowpattern '/self' does NOT work

7. 'allow zero length' not working

8. 'Cancel' does not work

9. in WRITETEXT, 'string' + @variable not working

10. 'INSERT' query not working

11. 'Go to portal row' not working

12. doe's d3nt 7.2 work on xp


 
Powered by phpBB® Forum Software