> -----Original Message-----
> From: Jochen Westland [mailto:jochen(dot)westland(at)invigo(dot)de]
> Sent: 08 July 2002 16:33
> To: Dave Page
> Subject: AW: [ODBC] HELP!! #DEFINE NAMEDATALEN 128 in
> postgres_ext.h causes ODBC-ERROR(s) ??
> hi dave,
> thanks a lot for your message, i'm looking forward for
> some good news :)
> Just one thing, keep in mind that MSaccess fails as well as
> pgadmin does, what makes me somehow sure, that that is a
> odbc-driver problem in first instance...
Yes, that's what I'm currently looking at. My tests give:
conn=51783144, query='SELECT c.oid, c.relname,
pg_get_userbyid(c.relowner) AS viewowner, c.relacl,
pg_get_viewdef(c.oid) AS definition FROM pg_class c WHERE
((c.relhasrules AND (EXISTS (SELECT r.rulename FROM pg_rewrite r WHERE
((r.ev_class = c.oid) AND (bpchar(r.ev_type) = '1'::bpchar))))) OR
(c.relkind = 'v'::"char")) AND relnamespace = 2200::oid ORDER BY
[ fetched 8 rows ]
conn=51783144, query='SELECT relname, n_tup_ins, n_tup_upd, n_tup_del
FROM pg_stat_all_tables ORDER BY relname'
[ fetched 107 rows ]
The 1th item was truncated
The buffer size = 33 and the value is
In the commlog. The 'The 1th item was truncated' message comes from the
ODBC driver so I'll have to let someone who understands it's internal
more than me figure it out.
I *hope* that pgAdmin will work OK though when the driver does - there
are no set limits on string length in it so it *should* just work -
though it will probably slow down with very long names because it has to
encode them into upper case internally which doubles the length in
storage and slows things down a bit.
pgsql-odbc by date
|Next:||From: Rod Enke||Date: 2002-07-09 00:48:55|
|Subject: Re: Performance of ODBC-Driver /w IIS5.0/ColdFusion|
|Previous:||From: Dave Page||Date: 2002-07-08 15:09:41|
|Subject: Re: HELP!! #DEFINE NAMEDATALEN 128 in postgres_ext.h causes ODBC-ERROR(s) ??|