Dave Page wrote:
>
> > -----Original Message-----
> > From: Hiroshi Inoue [mailto:Inoue@tpf.co.jp]
> > Sent: 27 June 2001 09:08
> > To: pgsql-odbc@postgresql.org
> > Subject: [ODBC] an ODBC change
> >
> >
> > Hi all,
> >
> > I've just committed a fix(Support procedure calls).
> > Now the version is 7.01.0006.
> >
>
> Hi Hiroshi,
>
> Did you get a chance to look at splitting long info messages (>512Kb) to
> allow multiple calls to SQLError to retrieve them yet?
>
...
cn.Open
sSQL = "EXPLAIN SELECT " & _
... your long query ...
cn.Execute (sSQL)
Debug.Print cn.Errors(0); "!!!"; cn.Errors(1)
The output is as follows.
NOTICE: QUERY PLAN:
Hash Join (cost=599.84..612.33 rows=7 width=148)
-> Seq Scan on pg_type t (cost=0.00..4.88 rows=188 width=36)
-> Hash (cost=599.82..599.82 rows=7 width=112)
-> Nested Loop (cost=0.00..599.82 rows=7 width=112)
-> Seq Scan on pg_class c (cost=0.00..593.70 rows=1
width=58)
SubPlan
-> Seq Scan on pg_rewrite (cost=0.00..3.28
rows=1 width=32)
-> Index Scan using pg_attribute_relid_attnum_index on
p!!!g_attribute a (cost=0.00..6.06 rows=5 width=54)
regards,
Hiroshi Inoue
