Hi David,
I'm having real trouble figuring this one out. I've tried it on 95 & 98 and
on PostgreSQL 6.4 & 6.4.2 and cannot reproduce this error at all. I have
added code to handle if no default value can be found, but this should never
happen because the existing code will only try to get the default value if
the attribute record (pg_attribute.atthasdef) is true.
I'm not sure if this is because I've misunderstood the way PostgreSQL works
or there's some corruption in your system.
Any suggestions gratefully received :-)
Dave.
--
Dave Page, Network & Systems Manager, The Vale Housing Association Ltd.
dpage@vale-housing.co.uk
http://www.vale-housing.co.uk (Work)
http://www.vale-it.demon.co.uk/ (Home of pgAdmin)
Beer can be a permanent solution - but only if you have enough of it!
> -----Original Message-----
> From: David Hartwig [mailto:daveh@insightdist.com]
> Sent: 12 February 1999 15:13
> To: Dave Page
> Cc: pgsql-interfaces@postgreSQL.org
> Subject: Re: [INTERFACES] pgAdmin v6.4.2
>
>
>
>
> Dave Page wrote:
>
> >
> > > However, there is one item that you may want to address.
> > > While browsing
> > > through the Schema Tables, if I click on a column name I
> > > often get an error.
> > > "Error 3021, No current record." Perhaps I am doing
> > > something incorrect.
> > > The message only occurs when there in NO default value for
> > > the column. I
> > > inspected the ODBC driver CommLog and observed that, in
> > > fact, pgadmin was
> > > querying for these default values and was returning an empty
> > > record sets.
> > > This does not seem as if it should be considered an error
> condition.
> >
> > I'll look into this. I can't seem to reproduce it though,
> so if you could
> > send me your CommLog and the c:\pgerr.log file it would be a help.
> >
>
> I have attached them both. Notice in the CommLog, the last
> query. I have
> verified that no row meets the specified criteria. Only
> columns with DEFAULT
> values seem to have entries in pg_attrdef.