Understanding generated classes
For every recordset definition you create in VenturaSQL Studio, a recordset class is generated.
The generated recordset class gets the recordset name you entered in VenturaSQL Studio. The name always ends with the word "Recordset". For example "CustomersRecordset".
Depending on the number of resultsets the SQL script produces, different class structures are generated. There is a difference between zero, one and multiple resultsets:
A resultset is a collection (list) of records
The Recordset.SaveChanges method is only generated for recordsets that are updateable. Read-only recordsets do not have a SaveChanges method.
See topic VenturaSQL Studio > SQL script view for information on making recordsets updateable.
Client API documentation
Depending on the SQL script and defined parameters, a recordset class may contains nested-classes. The nested classes are for parameters, multiple resultsets and records.
In the Client API documentation there are 3 topics that describe all the nested-classes, properties, methods and events you encounter in a recordset class:
- Recordset (generated class) documentation
- Resultset (generated class) documentation
- Record (generated class) documentation
The names Recordset, Resultset and Record are not the class names that are generated. The actual class names are derived from the recordset definition name and (optionally) resultset names.
A record represents a database row and has column properties.