TileDB Error reporting mechanism is not thread safe about tiledb HOT 4 CLOSED

Internal to TileDB, I think we should switch to using exceptions. We can catch these exceptions at the c-api boundry and map them to error codes. This doesn't fix the problem, but it is a step in the right direction.

A less dramatic option would be to switch to a Status object which would preserve the error code like model but carry the error message internal to the object.

from tiledb.

The Status object route was chosen, as switching to exceptions was deemed too radical change at this time.

#55 helped with this, but the c api still relies on a global buffer.

from tiledb.

I suggest we make the C API functions return a tiledb_error_t (opaque) object as discussed in #30, which has a pointer to the last Status object returned (which is local to each thread). Then the API functions that operate on tiledb_error_t can make use of it.

from tiledb.

closed by #60

from tiledb.