Macromedia dreamweaver 8-using dreamweaver User Manual
984
Appendix A: Beginner’s Guide to Databases
A subset of data extracted from one or more tables is called a recordset (or a DataSet in
ASP.NET). A recordset is also a table because it’s a collection of records that share the same
columns. For example, a hockey team roster listing the names and positions of the players
could be called a recordset: it consists of a subset of all the possible information about the
players, including goals, assists, penalty minutes, and so on.
ASP.NET). A recordset is also a table because it’s a collection of records that share the same
columns. For example, a hockey team roster listing the names and positions of the players
could be called a recordset: it consists of a subset of all the possible information about the
players, including goals, assists, penalty minutes, and so on.
To create a recordset, you run a database query. A query consists of search criteria. For
example, the query can specify that only certain columns be included in the recordset, or that
only certain records be included. For more information, see
example, the query can specify that only certain columns be included in the recordset, or that
only certain records be included. For more information, see
Related topics
■
Database design basics
Database design is the first step in building any database-driven website. This section presents
a case study to explain basic database design principles. The case study involves a web
application commissioned by a fictional company called Arrow Aircraft Services, a firm that
manages a small fleet of privately owned business jets.
a case study to explain basic database design principles. The case study involves a web
application commissioned by a fictional company called Arrow Aircraft Services, a firm that
manages a small fleet of privately owned business jets.
Database design consists of a series of common steps. First, study the business rules and
policies to be reflected in the web application. Second, consider the questions users will ask
the database. Third, define the structure of the database. Finally, create the database.
policies to be reflected in the web application. Second, consider the questions users will ask
the database. Third, define the structure of the database. Finally, create the database.
Number
Database table
LastName FirstName
Position
Goals
Recordset table
LastName FirstName
Position