@beberlei I know about the inconsistencies when using `rowCount` for `SELECT` statements. I will add the desired method in the platform but before I do that there is another issue that came up recently with this patch. The patch enables row count retrieval but I encountered memory exhaustion errors when working with very large resultsets. This is due to calling `sasql_stmt_store_result()` which puts the results into memory. Now I don't see a solution to fix both issues. The only idea I have here is to call `sasql_stmt_store_result()` "on demand" in `SQLAnywhereStatement::rowCount()`. Then you could still work with large resultsets (if you don't need to know the row count) and use row count for resultsets that fit into memory. I have not tested this yet but if it works this could solve most common use cases I think as working with such large resultsets causing a PHP out of memory error should be an edge case IMO. I could an entry to the known vendor issues for that case then. What do you think?