pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feednot translating a query properly. . .
3+ messages / 3 participants
[nested] [flat]
* not translating a query properly. . .
@ 1999-04-30 16:50 JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
0 siblings, 0 replies; 3+ messages in thread
From: JT Kirkpatrick @ 1999-04-30 16:50 UTC (permalink / raw)
To: 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>
here is my psqlodbc log -- it's short. i have two problems (or may just
one). it still shows using version 6.3, but i completely removed 6.3 (in
add/remove programs) and reinstalled 6.4. the other problem i am having is
shown in it too -- i am in an access97 query sql view typing "select subnum
from subs union all select vnum from vend;" (which works great from the
psql prompt), but i am getting some kind of syntax error message. if you
take the time to look into the file you'll also see another ongoing problem
i am having with booleans in my queries (where i am trying to show all
records that are 't' or =1 or any other way i try -- i just bombs). is
there any reason why this query wouldn't run properly? i thought upgrading
to the new version might help. . .
jt
Attachments:
psqlodbc.log (application/octet-stream, 2.9K) download
^ permalink raw reply [nested|flat] 3+ messages in thread
* RE: [INTERFACES] not translating a query properly. . .
@ 1999-04-30 19:19 Michael J Davis <michael.j.davis@tvguide.com>
0 siblings, 1 reply; 3+ messages in thread
From: Michael J Davis @ 1999-04-30 19:19 UTC (permalink / raw)
To: 'JT Kirkpatrick' <jt-kirkpatrick@mpsllc.com>; 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>
I would suggest either changing the protocol from 6.3 to 6.4 in the
PostgreSQL ODBC driver. My other suggestion was to upgrade the PostgreSQL
ODBC driver but it sounds like you have already done that. I believe the
version you are seeing is the version of the ODBC driver and not the
database server. I am assuming you are using PostgreSQL 6.4.2 or better.
Booleans are another issue. Access97 treats boolean values as int2. It
expects a -1 for true and 0 for false. PostgreSQL treats them as a character
('t' for true and 'f' for false). This means that the word TRUE in Access97
is a -1 and not the 't' that PostgreSQL is expecting. You have two choices
the MS way or the PostgreSQL way. I converted all my booleans to int2 in
PostgreSQL. This was not my first choice but I did not have to change all
of the Access97 queries and code that interacted with boolean values.
-----Original Message-----
From: JT Kirkpatrick [SMTP:jt-kirkpatrick@mpsllc.com]
Sent: Friday, April 30, 1999 10:51 AM
To: 'pgsql-interfaces@hub.org'
Subject: [INTERFACES] not translating a query properly. . .
here is my psqlodbc log -- it's short. i have two problems (or may
just
one). it still shows using version 6.3, but i completely removed
6.3 (in
add/remove programs) and reinstalled 6.4. the other problem i am
having is
shown in it too -- i am in an access97 query sql view typing "select
subnum
from subs union all select vnum from vend;" (which works great from
the
psql prompt), but i am getting some kind of syntax error message.
if you
take the time to look into the file you'll also see another ongoing
problem
i am having with booleans in my queries (where i am trying to show
all
records that are 't' or =1 or any other way i try -- i just bombs).
is
there any reason why this query wouldn't run properly? i thought
upgrading
to the new version might help. . .
jt << File: psqlodbc.log >>
^ permalink raw reply [nested|flat] 3+ messages in thread
* RE: [INTERFACES] not translating a query properly. . .
@ 1999-04-30 21:11 Hugh Lawson <hglawson@nr.infi.net>
parent: Michael J Davis <michael.j.davis@tvguide.com>
0 siblings, 0 replies; 3+ messages in thread
From: Hugh Lawson @ 1999-04-30 21:11 UTC (permalink / raw)
To: Michael J Davis <michael.j.davis@tvguide.com>; +Cc: 'JT Kirkpatrick' <jt-kirkpatrick@mpsllc.com>; 'pgsql-interfaces@hub.org' <pgsql-interfaces@hub.org>
I also had a problem with initdb creating 6.3 type databases after I
had compiled and installed the pgsql 6.4 source. I had not completely
removed all traces of 6.3. In particular, super-user postgres home
address was RedHat style /var/lib whatever, and there were still some
files there.
After I deleted the postgres user and made sure everything was gone,
then initdb worked properly. I went back to 6.3 anyway because I
couldn't get pgaccess working in 6.4, and some other problems, and I
was frazzled from the unaccustomed work of setting up from sources.
Spoiled by rpm, I guess.
I'll try again now that I've learned that there is an escape route.
Fortunately for me this is all hobby, and I don't have anybody
depending on my db.
Incidentally, suse 5.2 has "wish" not in /usr/bin as specified in the
stock pgaccess script. (I also fiddle with a suse distribution.) I
solved this with a bash script that contained "wish -f <path to
pgaccess>".
Hugh Lawson
Greensboro, North Carolina
hglawson@nr.infi.net
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~1999-04-30 21:11 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-04-30 16:50 not translating a query properly. . . JT Kirkpatrick <jt-kirkpatrick@mpsllc.com>
1999-04-30 19:19 RE: [INTERFACES] not translating a query properly. . . Michael J Davis <michael.j.davis@tvguide.com>
1999-04-30 21:11 ` Hugh Lawson <hglawson@nr.infi.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox