From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | pgsql-odbc <pgsql-odbc(at)postgresql(dot)org> |
Subject: | RE: Error handling in ODBC |
Date: | 2001-06-14 10:38:46 |
Message-ID: | 8568FC767B4AD311AC33006097BCD3D61A2C41@woody.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: Hiroshi Inoue [mailto:Inoue(at)tpf(dot)co(dot)jp]
> Sent: 14 June 2001 11:09
> To: Dave Page
> Cc: Zoltan Kovacs; pgsql-odbc
> Subject: Re: [ODBC] Error handling in ODBC
>
>
> Dave Page wrote:
> >
>
> [snip]
>
> >
> > As far as I can tell, it is then not possible to access the notice
> > from a client app (cetainly SQLError won't return it in my
> test prog,
> > yet I can quite happily get a real error from an invalid query for
> > example.
> >
>
> Hmm it may be possible that SQLERROR returns a notice message
> in an appropriate condition(?????) though I'm not sure.
Unfortunately I'm not really familiar enough with either C or the guts of
the driver to know or be able to figure out in a reasonable amount of time
(though I have spent hours staring at the code :-)) what exactly it is/is
trying to do. I do know it's not doing what I need it to :-(, and - I
suspect - what it should be doing (though these are not necessarily one and
the same).
Any suggestions from those more experienced in these things would be
greatfully received....
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | postgresql | 2001-06-14 11:51:50 | odbc on a mac |
Previous Message | Hiroshi Inoue | 2001-06-14 10:08:46 | Re: Error handling in ODBC |