You shouldn't have to care. The status vector is a well defined, self
describing data structure. A transmission protocol should pass it, not
interpret it. If you have to get involved in the semantics, you're either
doing something wrong (or somebody screwed up the architecture).
That said, the philosophy is that the frst code is primary -- something an
application programmer can make part of his application logic. The
secondary codes are the details which are likely to be implementation and
version specific. Secondary codes are most useful for debugging and
unexpected error diagnosis.
On Saturday, June 28, 2014, Mark Rotteveel <m...@lawinegevaar.nl> wrote:
> I am working on replacing the protocol implementation, and now I am
> running into a 'problem' with parsing the status vector (or actually
> with the result of that parse).
>
> Currently I treat each isc_arg_gds and isc_arg_warning as a separate
> exception that is chained to the previous exception, but it looks like
> the statusvector contains only a single error that is constructed from
> multipe isc_arg_* entries (including isc_arg_gds).
>
> Is this indeed the case, or can the status vector contain multiple
> independent errors? If so is there a way to identify when the next error
> starts?
>
> A separate problem is identifying the most specific error. I notice that
> the head of the status vector has the least specific error code (eg
> isc_dsql_error instead of isc_dsql_field_err for a "Column unknown") is
> there an algorithm to determine the most specific error code or do I
> need to apply some heuristic (eg if the errorcode is isc_dsql_error then
> use the next error code, or always use the last one).
>
> Mark
> --
> Mark Rotteveel
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> Firebird-Devel mailing list, web interface at
> https://lists.sourceforge.net/lists/listinfo/firebird-devel
>
--
Jim Starkey
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
