Foundations of Programming - Karl Seguin

Chapter 3 - Persistence
public class Upgrade
{
private int _id;
private string _name;
private string _description;
private decimal _price;
private List _requiredUpgrades;
}
public int Id
{
get { return _id; }
internal set { _id = value; }
}
public string Name
{
get { return _name; }
set { _name = value; }
}
public string Description
{
get { return _description; }
set { _description = value; }
}
public decimal Price
{
get { return _price; }
set { _price = value; }
}
public List RequiredUpgrades
{
get { return _requiredUpgrades; }
}
We’ve added the basic fields you’d likely expect to see in the class. Next we’ll create the table that
would hold, or persist, the upgrade information.
CREATE TABLE Upgrades
(
Id INT IDENTITY(1,1) NOT NULL PRIMARY KEY,
[Name] VARCHAR(64) NOT NULL,
Description VARCHAR(512) NOT NULL,
Price MONEY NOT NULL,
)
No surprises there. Now comes the interesting part (well, relatively speaking), we’ll start to build up our
data access layer, which sits between the domain and relational models (interfaces left out for brevity)
Foundations of Programming Copyright © Karl Seguin www.codebetter.com
21