The two line below are represented in the same way in the debuger. But in the former case, there are many thousands Rows, and in the later case, there is only 1 Row.
rowsFound = db.SelectSQL("SELECT * FROM Domiciliation;")
Break
rowsFound = db.SelectSQL("SELECT * FROM Domiciliation WHERE ID=" + Unique_ID.ToString + ";")
Break
a rowSet is the currentRow (contents) and extra info (columnCount and if you are at the end etc)
you can move along you rowset (move next) to get the new contents (if any) and update the extra info
itâs not an array. And in any language is not an array
You can convert the rowset to any data structure you need (array of dictionaries, xml, json, two dimension array of variant) but its up to you
Iâm confused. In your initial post you said there was a difference. You got thousands of rows in the first query, and 1 row in the second. That is to be expected.
Emile wants to see the number of rows the RowSet has in the debugger, similar to what Arrays show. Instead of just RowSet:
something like RowSet(1000) or RowSet(0):
The âcurrent rowâ isnât shown because itâs not a true number at all. If you do a query with a definitive row ID then you get a rowset with just one row. CurrentRow is a pointer to that row. Itâs not anything to do with the contents of the record. It isnât, for example, the ID of the record. Not all database engines have an ID column, some donât even have a single unique column. The primary key is what identifies the row uniquely. It can often be made up of more than one column.
You can see the data from the current Row by clicking contents, which I think youâve spotted.
The concept of âcurrent rowâ is foreign to RowSet. It is whatever row you have moved to. You cannot jump to a specific row in the RowSet, so having that information is pointless.
The debugger doesnât display RowCount because it is not supported for all databases. Youâll need to set a local variable to RowCount if you want to see it in the debugger.