Skip to content

Bug: kuzu_query_result_to_string is advancing the wrong iterator #5973

@dtenny

Description

@dtenny

Kuzu version

v0.11.3.16

What operating system are you using?

Fedora 41 x86_64

What happened?

Sometime betwewen V0.11.2.2 and V0.11.3.16, breaking changes were made to kuzu_query_result_to_string. In the past, this did not advance the iterator state on the query result, but now it does, and it is causing a large volume of breakage in my API tests which use the various to_string methods as the basis of comparison to processing of tuples that follows.

This code may or may not be responsible, if it isn't responsible it looks like a related bug:
https://github.com/kuzudb/kuzu/blame/45a8b887e565e43f006002004dc3923bd7397798/src/main/query_result/materialized_query_result.cpp#L81-L83

Are there known steps to reproduce?

Generate a query result (using the C API, such as by the example at https://docs.kuzudb.com/get-started/). Before iterating through the tuples, call kuzu_query_result_to_string. In V0.11.2.2 the tuple iteration would see the tuples after the to_string call. In V0.11.3.16 use of the to_string method means no further tuple processing will occur.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions