On Mon, 31 Jan 2000, Patrick Hayes wrote:
> What do you think? Four/five fairly simplistic global functions, lookup
> tables giving code meanings, and adding a little chunk of code to existing
> functions to let them report what goes wrong.
It certainly seems thorough. But I'm not sure on what this call chain
would be, really. Not every PHP function, since we're not likely
to get any cooperation from them. And Midgard-PHP functions are
only likely to call internal API calls which are not going to
be meaningfull to the PHP developer.
Having one error context per function (holding an error reason,
possibly an error message) or even just a single error context
would cover my needs satisfactorily.
> Emile: on an unrelated note, I don't think ODBC handles anything fancy like
> streaming (correct me if I'm wrong, anybody!). ODBC is basically
> _Microsoft's_ view of database operations a few years back, so it's fairly
> simplistic. If older versions of Sql Server didn't have streaming (and I
> doubt they did), ODBC won't either.
*sigh* You're right. I've looked it up, no streaming. Well, looks like
BLOB chunking (as per earlier proposal on the list) is going to be used
for all DB blobs then.
Emile
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
