What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

When SQLFetch() reach SQL_NO_DATA_FOUND, It will not return error when SQLFetch() is called again.

What would you like to see happen?

Describe the desired outcome or enhancement.

I expected SQLFetch() will always return SQL_NO_DATA_FOUND, when it reach the end of the rowset.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

it affects my project

What steps, if any, are you taking today to manage this problem?

We use mongo DB Atlas SQL odbc driver 2.0.01

1) call SQLTableW(“qualifiername”,“”,“”,“”)

2) call SQLFetch() to fetch all the data

3) when SQLFetch() returns SQL_NO_DATA_FOUND, we call SQLFetch() again, it will returns below error:

2026-01-16 07:16:57 - ERROR: [Env_0x13bf5080][Conn_0x13bf5920][Stmt_0x13bf4220] SQLFetch:: [MongoDB][API] Caught panic: called Option::unwrap() on a None value

Ok(“in file ‘core\src\collections.rs’ at line 230”)

4) the issue only occurs on sqlTableW() to fetch table list. If we run a sql query "select * from city", then we use SQLFetch() to get data. When cursor reaches the end , SQL_NO_DATA_FOUND is returned SQLFetch() is called again.