pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
PsqlODBC broken due to int4out(usesysid)
3+ messages / 2 participants
[nested] [flat]

* PsqlODBC broken due to int4out(usesysid)
@ 2000-10-02 15:36 Patrick Welche <prlw1@newn.cam.ac.uk>
  2000-10-02 17:10 ` Re: PsqlODBC broken due to int4out(usesysid) Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 3+ messages in thread

From: Patrick Welche @ 2000-10-02 15:36 UTC (permalink / raw)
  To: pgsql-interfaces

The aim is to import a table from postgresql into M$ access using
PsqlODBC v06-50-0000. This is with
 PostgreSQL 7.1devel on i386-unknown-netbsdelf1.5E, compiled by GCC egcs-1.1.2
source code of 14 August.

Problem: the pointy clicky box appears with no tables to select for import as
the driver sends:

select relname,usename,relhasrules
 from pg_class,pg_user
 where relkind = 'r'
 and relname !~'^xinv[0-9]+'
 and int4out(usesysid)= int4out(relowner)
 order by relname;

Reason: AFAICT it really doesn't want "int4out"..

select relname,usename,relhasrules
 from pg_class,pg_user
 where relkind = 'r'
 and relname !~'^xinv[0-9]+'
 and usesysid = relowner
 order by relname;

works fine.. Can someone fix please?

Cheers,

Patrick



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: PsqlODBC broken due to int4out(usesysid)
  2000-10-02 15:36 PsqlODBC broken due to int4out(usesysid) Patrick Welche <prlw1@newn.cam.ac.uk>
@ 2000-10-02 17:10 ` Tom Lane <tgl@sss.pgh.pa.us>
  2000-10-02 17:45   ` Re: PsqlODBC broken due to int4out(usesysid) Patrick Welche <prlw1@newn.cam.ac.uk>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2000-10-02 17:10 UTC (permalink / raw)
  To: prlw1@cam.ac.uk; +Cc: pgsql-interfaces

Patrick Welche <prlw1@newn.cam.ac.uk> writes:
> Reason: AFAICT it really doesn't want "int4out"..

Yup, the odbc driver is already fixed in current sources (and
back-patched so it will be in 7.0.3).

In the long run it'd be nice if the backend either handled this sort
of query correctly or at least raised an error, but that's probably
not going to happen for 7.1.  We'll need some way of declaring in the
datatype system what kind of data the outputs of output-conversion
functions really are.  Various people (including me) have muttered
about this off-and-on, but no one's put forward a complete proposal.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: PsqlODBC broken due to int4out(usesysid)
  2000-10-02 15:36 PsqlODBC broken due to int4out(usesysid) Patrick Welche <prlw1@newn.cam.ac.uk>
  2000-10-02 17:10 ` Re: PsqlODBC broken due to int4out(usesysid) Tom Lane <tgl@sss.pgh.pa.us>
@ 2000-10-02 17:45   ` Patrick Welche <prlw1@newn.cam.ac.uk>
  0 siblings, 0 replies; 3+ messages in thread

From: Patrick Welche @ 2000-10-02 17:45 UTC (permalink / raw)
  To: pgsql-interfaces

On Mon, Oct 02, 2000 at 01:10:47PM -0400, Tom Lane wrote:
> Patrick Welche <prlw1@newn.cam.ac.uk> writes:
> > Reason: AFAICT it really doesn't want "int4out"..
> 
> Yup, the odbc driver is already fixed in current sources (and
> back-patched so it will be in 7.0.3).

Great! - is a compiled driver available anywhere? (I haven't tried
cross-compiling before..  (NetBSD->M$))

On the other hand copy table to 'file' using delimiters ','; works fine too!

Cheers,

Patrick



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2000-10-02 17:45 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-10-02 15:36 PsqlODBC broken due to int4out(usesysid) Patrick Welche <prlw1@newn.cam.ac.uk>
2000-10-02 17:10 ` Tom Lane <tgl@sss.pgh.pa.us>
2000-10-02 17:45   ` Patrick Welche <prlw1@newn.cam.ac.uk>

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