Warning messages may be inaccurate in Explorer

[mewim]

Currently the warning messages are stored at connection level. However, Explorer uses a connection pool to allow multiple concurrent queries. If the user is running multiple queries concurrently, the result from CALL SHOW_WARNINGS() may be inaccurate. One potential workaround is to limit to one connection only (by modifying KUZU_NUM_CONNECTIONS).

[ray6080]

hmm Can we make use of queyr_id in the returned result for this?

[mewim]

I think the issue is that in the case of multiple connections, if the CALL is sent to a different connection, it would not have the expected result.

[ray6080]

I see. Yeah, make sense.