Skip to content

Multi resultset consistency - #130

Open
smavros wants to merge 4 commits into
MonetDB:masterfrom
smavros:multi-resultset-consistency
Open

smavros wants to merge 4 commits into
MonetDB:masterfrom
smavros:multi-resultset-consistency

Conversation

@smavros

@smavros smavros commented Mar 3, 2026

Copy link
Copy Markdown
Contributor

implements proposal of #129

one thing that still bothers me is the interface of cursor._store_result() and particularly the update_existing bool parameter. I understand that this is used for the caching functionality (see the call at cursor._populate_cache()) but I'm not sure if we will ever encounter a _store_result() call with a block that contains an empty result set (due to a DDL/DML statement) together with a update_existing=True. I think not but not 100% sure. Any input's welcome 🙂

@smavros
smavros requested a review from joerivanruth March 3, 2026 12:56
smavros added 2 commits March 3, 2026 14:30
For DDL/DML we could simply have an empty list of descriptions but it
seems that this does not adheres to the PEP-0249 which requires
description attribute to be `None` in case of an operations which does
not return any rows
DDL/DML mapi messages do not include a query id. If we want to have an
empty result set in the result sets set then we need to support `None`
query_ids
@smavros

smavros commented Mar 3, 2026

Copy link
Copy Markdown
Contributor Author

not sure why the TLS support test is failing or how to fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant