C H A P T E R 4 Designing Database E-Commerce

1. C H A P T E R 4 Designing Database E-Commerce Hassanin M. Al-Barhamtoshy hassanin@kau.edu.sa

2. How This Chapter Is Structured The main topics we’ll touch on in this chapter are: • Analyzing the requirement of the databaseand the functionality it should support • Creating the database structures for the application • Implementing the business tier objects required to make the system run, and putting a basic but functional error-handling strategy in place • Implementing a functional UI for the system

3. What Does a Product Catalog Look Like? • We need the following file entities: • Products • Categories • Customers • Orders

4. Database Designing The major tables in e-Commerce database, as the following: 1- Products Table Name Category Name Description Vendor name Vendor address Vendor phone number Price Image file name

5. Database Designing 2- Category Name 3- Customers Last Name First Name Address City State Zip Code Phone Number E-mail Credit Card Number

6. Database Designing 4- Order Order number Date Customer Product Quantity Price Subtotal Shipping Tax Total

7. After the key columns have been added, the list looks like this: Products Product ID (primary key) Name Category ID (foreign key) Category Name Description Price Image file name Vendor ID (foreign key) Vendor Vendor ID (primary key) Name Address City State Zip Code Phone Number E-mail

8. Category Category ID (primary key) Name Customers Last Name First Name Address City State Zip Code Phone Number E-mail (primary key) Credit Card Number Order Order number (primary key) Date

9. Order Order number (primary key) Date Customer ID (foreign key) Product ID (foreign key) Quantity Price Subtotal Shipping Tax Total

10. Entity Relation Database

11. Building a Product Catalog Application This application’s user interface has just three pages: • Default.aspx displays a list of products for a category selected by the user. • Product.aspx displays details about a specific product selected by the user. • Cart.aspx is displayed when the user chooses to purchase a product.

12. The user interface for the Product Catalog application.

13. The Product List page.

14. The Product Detail page.

15. The Cart page

16. Designing the Product Database It consists of three tables: Categories Products FeaturedProducts

17. The Categories table

18. The Products table

19. The Featured Products table

20. Creating the database sqlcmd -S localhost\SQLExpress -i CreateProducts.sql The CreateProducts.sql script USE master GO IF EXISTS(SELECT * FROM sysdatabases WHERE name=’Products’) DROP DATABASE Products GO CREATE DATABASE Products ➝3 ON (NAME= Product, FILENAME= ‘C:\APPS\Products.mdf’, SIZE=10 ) GO

21. Creating the database USE Products GO CREATE TABLE Categories ( catid VARCHAR(10) NOT NULL, name VARCHAR(50) NOT NULL, [desc] VARCHAR(MAX) NOT NULL, PRIMARY KEY(catid) ) GO CREATETABLE Products (productid VARCHAR(10) NOT NULL, catid VARCHAR(10) NOT NULL, name VARCHAR(50) NOT NULL, shorttext VARCHAR(MAX) NOT NULL, longtext VARCHAR(MAX) NOT NULL, price MONEY NOT NULL, thumbnail VARCHAR(40) NOT NULL, image VARCHAR(40) NOT NULL, PRIMARY KEY(productid), FOREIGN KEY(catid) REFERENCES Categories(catid) ) GO

22. Creating the database CREATE TABLE FeaturedProducts ( productid VARCHAR(10) NOT NULL, featuretext VARCHAR(MAX) NOT NULL, saleprice MONEY NOT NULL, PRIMARY KEY(productid), FOREIGN KEY(productid) REFERENCES Products(productid) ) GO

23. Adding Logic to the Site The following paragraphs describe the highlights of this script: • Sets the database context to master. This is usually the default context, but it’s a good idea to set it just in case. • Deletesthe existing Products database if it exists. • Createsa database named Products. The database file will be created in the C:\Apps directory. You should change this location if you want to place the database file in a different folder. • Createsthe Categories table. • Note that the column name desc is a SQL keyword, so it must be enclosed in brackets. • Createsthe Products table. • Createsthe FeaturedProducts table.

24. Adding some test data sqlcmd -S localhost\SQLExpress -i InsertProducts.sql • Once again, you’ll need to change the server name if you’re not running SQL Server Express on your own computer. • You’ll know the script works if you see a series of messages like this one: (1 rows affected)

25. Adding some test data

26. Querying the database The application must perform the following queries: • Retrieveall rows from the Categories table to fill the drop-down list on the Default.aspx page so the user can select a product. • Retrieve all rows from the FeaturedProducts table to display at the top of the Default.aspx page. Note that some data is also required from the Products table, so this query requires a join. • Retrieveall products for a given category, including the sale price indicated in the FeaturedProducts table. • Retrieve all data for a specified product to display on the Product.aspx page. Note that this query must also retrieve the sale price from the FeaturedProducts table.

27. Querying the database • The query to retrieve all rows from the Categories table uses this SQL statement: SELECT catid, name, [desc] FROM Categories ORDER BY name

28. Querying the database • The query to retrieve the featured product rows requires a join to retrieve data from the FeaturedProducts table as well as the Products table: SELECT FeaturedProducts.productid, FeaturedProducts.featuretext, FeaturedProducts.saleprice, Products.name, Products.price FROM FeaturedProducts INNER JOIN Products ON FeaturedProducts.productid = Products.productid

29. Querying the database • The query to retrieve the products for a given category also requires a join: SELECT Products.productid, Products.catid, Products.name, Products.shorttext, Products.longtext, Products.price, Products.image, Products.thumbnail, FeaturedProducts.saleprice FROM Products LEFT OUTER JOIN FeaturedProducts ON Products.productid = FeaturedProducts.productid WHERE (Products.catid = @catid)

30. Querying the database • The last query used by the program retrieves the data for a specific product: SELECT Products.productid, Products.catid, Products.name, Products.shorttext, Products.longtext, Products.price, Products.image, FeaturedProducts.saleprice, FeaturedProducts.featuretext FROM Products LEFT OUTER JOIN FeaturedProducts ON Products.productid = FeaturedProducts.productid WHERE (Products.productid = @productid)”

31. Connecting to the database The connection string used to access the Products database is stored in the application’s web.config file, like this: <connectionStrings> <add name=”ConnectionString” connectionString=”Data Source=localhost\SQLExpress; Initial Catalog=Products;Integrated Security=True”/> </connectionStrings>

32. Querying the database • The last query used by the program retrieves the data for a specific product: SELECT Products.productid, Products.catid, Products.name, Products.shorttext, Products.longtext, Products.price, Products.image, FeaturedProducts.saleprice, FeaturedProducts.featuretext FROM Products LEFT OUTER JOIN FeaturedProducts ON Products.productid = FeaturedProducts.productid WHERE (Products.productid = @productid)”

33. Downloading the Code • Once you download the code, just decompress it with your favorite compression tool. Alternately, you can go to the main Wrox code download page at: www.wrox.com/dynamic/books/download.aspx to see the code available for this book and all other Wrox books. • You can also download the examples from the Wrox Books Web site at: http://eu.wiley.com/WileyCDA/WileyTitle/productCd-0764588079.html

34. Quiz # 2 • Design an ERD (Entity Relation Database) for e-Learning Application), includes the following: • E-Learning Table names. • Tables Structure. • Tables Relation.