[MonetDB-users] fetch_field errors.
Hello. I've been reading, in Mapi.mx, the following:
@item char **mapi_fetch_field_array(MapiHdl hdl)
Return an array of string pointers to the individual fields. A zero is returned upon encountering end of sequence or error. This can be analyzed in using @code{mapi\_error()}.
As I'm not a big fan of dynamic type checks, or dynamic error checks, I'd appreciate knowing: what kind of errors might this be? Any errors assuming anything might fail? Just to know... -- Guillaume Yziquel http://yziquel.homelinux.org/
Guillaume Yziquel a écrit :
Hello.
I've been reading, in Mapi.mx, the following:
@item char **mapi_fetch_field_array(MapiHdl hdl)
Return an array of string pointers to the individual fields. A zero is returned upon encountering end of sequence or error. This can be analyzed in using @code{mapi\_error()}.
As I'm not a big fan of dynamic type checks, or dynamic error checks, I'd appreciate knowing: what kind of errors might this be?
Any errors assuming anything might fail?
Just to know...
Moreover, I'm assuming that mapi_error should be called on the mapi connection data structure. Not on the query result datastructure. Am I right? If yes, is there a way to access the mapi connection datastructure pertaining to a given query result? Or should I keep track of it manually? All the best, -- Guillaume Yziquel http://yziquel.homelinux.org/
Guillaume Yziquel wrote:
Hello.
I've been reading, in Mapi.mx, the following:
@item char **mapi_fetch_field_array(MapiHdl hdl)
Return an array of string pointers to the individual fields. A zero is returned upon encountering end of sequence or error. This can be analyzed in using @code{mapi\_error()}.
As I'm not a big fan of dynamic type checks, or dynamic error checks, I'd appreciate knowing: what kind of errors might this be? That can be *any* error returned from the server. From illegal types, to assertion errors, to environmental errors (diskfull)....
Any errors assuming anything might fail?
Just to know...
Martin Kersten a écrit :
Guillaume Yziquel wrote:
Hello.
As I'm not a big fan of dynamic type checks, or dynamic error checks, I'd appreciate knowing: what kind of errors might this be?
That can be *any* error returned from the server. From illegal types, to assertion errors, to environmental errors (diskfull)....
OK. That a clear statement. Thank you very much. -- Guillaume Yziquel http://yziquel.homelinux.org/
participants (2)
-
Guillaume Yziquel -
Martin Kersten