On 8/25/22 21:52, Dimitry Sibiryakov wrote:
Perhaps warnings should be returned both ways: the binary form in
status and duplicate text in output. In this case applications will
get them as usual and advanced ones may be interested in parsing status.
I will look at what can be done here. Putting warnings (if any) into
status vector is definitely not a problem, duplicating them into text
output too, what may be not trivial is messages currently printed by
burp-like services to stdX.
Certainly we may require analyzing warnings from clients who want to
receive verbose messages in machine-readable form. Is it what you want?
Rather no. As written above - messages belong to (one of) output
streams (I believe services API should be able to deliver multiple
streams in parallel: messages and binary stream for backup as an
example).
I was thinking about it. Suppose adding N buffers for stream data
instead current one should not be too hard to do. But what about API for
that, format of data sent to user, etc. - that should be well though
before starting with this.
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
