Difference between revisions of "DD Class10"

esse quam videri
Jump to: navigation, search
(→‎Stored Porcedures)
(→‎Events and Commands)
 
(21 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
[[Category:Data Design]]
 
[[Category:Data Design]]
  
−
==Create a new user account==
+
==Primary Keys==
 +
The candidate key selected as being most important for identifying a body of information (an entity, object or record).
  
−
To insert into a new user we need to to combine three steps.  
+
==Normalization==
−
#INSERT into the People Table
+
[http://en.wikipedia.org/wiki/Database_normalization Normal Forms]
−
#Get the new PeopleID
 
−
#INSERT into the roles table
 
  
 +
'''First Normal'''
 +
:Form eliminates repeating groups by putting each into a separate table and connecting them with a one-to-many relationship.
 +
:
 +
 +
[[Data Relationships]]
 +
 +
Not Following First Normal Form Repeating Groups
 +
 +
Blog1
 +
{| class="wikitable" cellpadding="5" cellspacing="0"
 +
!BlogID !!  BlogText !! recCreationDate !! Mood
 +
|-
 +
|1 || Blog1 || 03/30/03 || Happy
 +
|-
 +
|2 || Blog2 || 03/30/03 || Happy
 +
|-
 +
|3 || Blog3 || 03/30/03 || Sad
 +
|-
 +
|4 || Blog4 || 03/30/03 || Happy
 +
|-
 +
|5 || Blog4 || 03/30/03 || Mad
 +
|}
 +
 +
Tables that Follow First normal form
 +
 +
Blog2
 +
{| class="wikitable" cellpadding="5" cellspacing="0"
 +
! BlogID !! BlogText !! recCreationDate !! MoodID
 +
|-
 +
|1 || Blog1 || 03/30/03 || 1
 +
|-
 +
|2 || Blog2 || 03/30/03 || 1
 +
|-
 +
|3 || Blog3 || 03/30/03 || 2
 +
|-
 +
|4 || Blog4 || 03/30/03 || 1
 +
|-
 +
|5 || Blog4 || 03/30/03 || 3
 +
|}
 +
Mood
 +
{| class="wikitable" cellpadding="5" cellspacing="0"
 +
!MoodID !! MoodName
 +
|-
 +
|1 || Happy
 +
|-
 +
|2 || Sad
 +
|-
 +
|3 || Mad
 +
|-
 +
|4 || Afraid
 +
|}
 +
 +
1NF also
 +
:Removes multiple column with the same type of data
 +
 +
Books Not Normal
 +
 +
'''Books'''
 +
{| class="wikitable" cellpadding="5" cellspacing="0"
 +
!Author !! Title_01 !! Pages_01 !! Title_02 !! Pages_02 !! Title_03 !! Pages_03
 +
|-
 +
| Michael Allen Dymmoch || The Man Who Understood Cats || 256 || White Tiger || 320 || ||
 +
|-
 +
| Joseph Cancellaro || Exploring Sound Design for Interactive Media || 272 || || || ||
 +
|}
 +
 +
In Class Build Blogs Table and Normalize Books Table
  
  
−
<sql>
 
−
INSERT into People
 
−
(salutationID, firstName, lastName, logonName, passwd)
 
−
values
 
−
(1, 'jeff', 'meyers', 'jmeyers', 'monkey')
 
−
</sql>
 
  
−
Check the new users PeopleID
+
http://en.wikipedia.org/wiki/First_normal_form
  
−
<sql>
+
==ERD==
−
SELECT PeopleID from People WHERE firstName = 'jeff' and lastName='meyers' and logonName='jmeyers'
 
−
</sql>
 
  
−
results PeopleID = 1
+
http://en.wikipedia.org/wiki/Entity-relationship_model
  
−
Give the new user a Role by inserting the PeopleID and a roleID into the roles table
+
tools
 +
*http://staruml.sourceforge.net/en/ free and open source
 +
*http://www.visual-paradigm.com/product/vpuml/ proprietary free community edition
  
−
<sql>
+
==Views==
−
INSERT into roles
 
−
( PeopleID, roleTypeID, RoleActive )
 
−
values
 
−
( 1, 1, 1)
 
−
</sql>
 
  
−
Since all of these steps need to happen or fail as a complete unit we must use an transaction. Of course in .NET there are several way to acomplish this.
+
UserTest
 +
{| class="wikitable" cellpadding="5" cellspacing="0"
 +
! UserID !! UserName !! LastLogon
 +
|-
 +
| 1 || jmeyers || 3/30/03
 +
|-
 +
|2 || bgates || 4/1/03
 +
|-
 +
|3 || sjobs || 4/2/03
 +
|-
 +
|4 || ltorvalds || 4/3/03
 +
|}
  
−
Test page one
 
  
−
Test page one with form
+
EmailTest
 +
{| class="wikitable" cellpadding="5" cellspacing="0"
 +
! EmailID !! UserID !! EmailAddress !! Active !! displayEmail
 +
|-
 +
| 1 || 1 || jeff@interactive.colum.edu || 1 || 0
 +
|-
 +
| 2 || 1 || only_a_test@hotmail.com || 0 || 0
 +
|-
 +
| 3 || 2 || bgates@microsoft.com || 1 || 0
 +
|}
  
−
===Stored Porcedures===
+
[INNER] JOIN
  
−
Default Template
+
The INNER JOIN returns all rows from both tables where there is a match. If there are rows in User that do not have matches in Email, those rows will not be listed.
  
 +
-- ANSI Style
 
<sql>
 
<sql>
−
-- ================================================
+
SELECT u.UserID,
−
-- Template generated from Template Explorer using:
+
u.UserName,
−
-- Create Procedure (New Menu).SQL
+
u.LastLogon,
−
--
+
e.EmailAddress,
−
-- Use the Specify Values for Template Parameters
+
e.active,
−
-- command (Ctrl-Shift-M) to fill in the parameter
+
e.displayEmail
−
-- values below.
+
FROM UserTest u
−
--
+
JOIN EmailTest e ON e.UserID = u.UserID
−
-- This block of comments will not be included in
+
</sql>
−
-- the definition of the procedure.
 
−
-- ================================================
 
−
SET ANSI_NULLS ON
 
−
GO
 
−
SET QUOTED_IDENTIFIER ON
 
−
GO
 
−
-- =============================================
 
−
-- Author: <Author,,Name>
 
−
-- Create date: <Create Date,,>
 
−
-- Description: <Description,,>
 
−
-- =============================================
 
−
CREATE PROCEDURE <Procedure_Name, sysname, ProcedureName>
 
−
-- Add the parameters for the stored procedure here
 
−
<@Param1, sysname, @p1> <Datatype_For_Param1, , int> = <Default_Value_For_Param1, , 0>,  
 
−
<@Param2, sysname, @p2> <Datatype_For_Param2, , int> = <Default_Value_For_Param2, , 0>
 
−
AS
 
−
BEGIN
 
−
-- SET NOCOUNT ON added to prevent extra result sets from
 
−
-- interfering with SELECT statements.
 
−
SET NOCOUNT ON;
 
  
−
    -- Insert statements for procedure here
+
--Theta style
−
SELECT <@Param1, sysname, @p1>, <@Param2, sysname, @p2>
+
<sql>
−
END
+
SELECT u.UserID,
−
GO
+
u.UserName,  
 +
u.LastLogon,
 +
e.EmailAddress,
 +
e.active,
 +
e.displayEmail
 +
FROM UserTest u,
 +
EmailTest e
 +
WHERE e.UserID = u.UserID
 
</sql>
 
</sql>
  
−
SProc to INSERT into people
+
results
  
−
<sql>
+
<pre>
−
-- ================================================
+
UserID      UserName            LastLogon                    EmailAddress                    active displayEmail
−
-- Template generated from Template Explorer using:
+
----------- ------------------- ----------------------------- -------------------------------- ------ ------------  
−
-- Create Procedure (New Menu).SQL
+
1          jmeyers            2003-03-30 00:00:00.000      jeff@interactive.colum.edu      1      0
−
--
+
1          jmeyers            2003-03-30 00:00:00.000      only_a_test@hotmail.com          0      0
−
-- Use the Specify Values for Template Parameters
+
2          bgates              2003-04-01 00:00:00.000      bgates@microsoft.com            1     0
−
-- command (Ctrl-Shift-M) to fill in the parameter
+
 
−
-- values below.
+
(3 row(s) affected)
−
--
+
</pre>
−
-- This block of comments will not be included in
 
−
-- the definition of the procedure.
 
−
-- ================================================
 
−
SET ANSI_NULLS ON
 
−
GO
 
−
SET QUOTED_IDENTIFIER ON
 
−
GO
 
−
-- =============================================
 
−
-- Author: Jeff
 
−
-- Create date:
 
−
-- Description:
 
−
-- =============================================
 
−
CREATE PROCEDURE PeopleInsert
 
−
-- Add the parameters for the stored procedure here
 
−
@salutationID int = 1,
 
−
@firstName varchar(50),
 
−
@lastName varchar(50),
 
−
@logonName varchar(50),
 
−
    @passwd varchar(50)
 
−
AS
 
−
BEGIN
 
−
-- SET NOCOUNT ON added to prevent extra result sets from
 
−
-- interfering with SELECT statements.
 
−
-- SET NOCOUNT ON;
 
  
−
    -- Insert statements for procedure here
+
LEFT [OUTER] JOIN
−
INSERT INTO People
 
−
(salutationID, firstName, lastName, logonName, passwd)
 
−
VALUES
 
−
(@salutationID, @firstName, @lastName, @logonName, @passwd)
 
−
END
 
−
GO
 
−
</sql>
 
  
−
test by running
+
The LEFT JOIN returns all the rows from the first table (User), even if there are no matches in the second table (Email). If there are rows in User that do not have matches in Email, those rows also will be listed.
  
 
<sql>
 
<sql>
−
PeopleInsert
+
SELECT u.UserID,
−
+
u.UserName,
−
@salutationID = 1,
+
u.LastLogon,
−
@firstName ='sprocTestFname',  
+
e.EmailAddress,
−
@lastName='sprocTestLname',
+
e.active,
−
@logonName ='sprocTestLogonName',
+
e.displayEmail
−
        @passwd ='monkey'
+
FROM UserTest u
 +
LEFT JOIN EmailTest e ON e.UserID = u.UserID
 
</sql>
 
</sql>
  
−
all one line is fine
+
<pre>
 +
UserID      UserName    LastLogon                EmailAddress                active displayEmail
 +
----------- ------------ ------------------------- ---------------------------- ------ ------------
 +
1          jmeyers      2003-03-30 00:00:00.000  jeff@interactive.colum.edu  1      0
 +
1          jmeyers      2003-03-30 00:00:00.000  only_a_test@hotmail.com      0      0
 +
2          bgates      2003-04-01 00:00:00.000  bgates@microsoft.com        1      0
 +
3          sjobs        2003-04-02 00:00:00.000  NULL                        NULL  NULL
 +
4          ltorvalds    2003-04-03 00:00:00.000  NULL                        NULL  NULL
 +
 
 +
(5 row(s) affected)
 +
</pre>
 +
 
 +
RIGHT [OUTER] JOIN
 +
 
 +
The RIGHT JOIN returns all the rows from the second table (Email), even if there are no matches in the first table (User). If there had been any rows in Email that did not have matches in User, those rows also would have been listed.
  
 
<sql>
 
<sql>
−
PeopleInsert @salutationID = 1, @firstName ='sprocTestFname', @lastName='sprocTestLname', @logonName ='sprocTestLogonName', @passwd ='monkey'
+
SELECT u.UserID,
 +
u.UserName,  
 +
u.LastLogon,
 +
e.EmailAddress,
 +
e.active,
 +
e.displayEmail
 +
FROM UserTest u
 +
RIGHT JOIN EmailTest e ON e.UserID = u.UserID
 
</sql>
 
</sql>
  
 +
results
  
−
GetPeopleID
+
<pre>
−
<sql>
+
UserID      UserName            LastLogon                    EmailAddress                    active displayEmail
−
CREATE PROCEDURE GetPeopleID
+
----------- ------------------- ----------------------------- -------------------------------- ------ ------------
−
-- Add the parameters for the stored procedure here
+
1          jmeyers            2003-03-30 00:00:00.000      jeff@interactive.colum.edu      1      0
−
@firstName varchar(50),
+
1          jmeyers            2003-03-30 00:00:00.000      only_a_test@hotmail.com          0      0
−
@lastName varchar(50),
+
2          bgates              2003-04-01 00:00:00.000      bgates@microsoft.com            1      0
−
        @logonName varchar(50)  
+
 
−
AS
+
(3 row(s) affected)
−
BEGIN
+
</pre>
−
-- SET NOCOUNT ON added to prevent extra result sets from
+
Making views in enterprise manager is easy. Just add the tables you want to join and click. It does all the typing for you.
−
-- interfering with SELECT statements.
+
 
−
SET NOCOUNT ON;
+
 
 +
==Review First Normal Form==
 +
 
 +
Let build the example for the homework.
 +
 
 +
==Build Interface to GameDB==
 +
 
 +
'''Games'''
 +
{| class="wikitable" cellpadding="5" cellspacing="0"
 +
!GameTitle !!  GameGenre !! DeveloperName !! Platform(s) !! Year !! DeveloperWebsite !! GameWebsite
 +
|-
 +
| Quake1 || FPS || id || Dos || 1996 || http://www.idsoftware.com/ || http://www.idsoftware.com/games/quake/quake/
 +
|-
 +
| Diablo|| RPG|| Blizzard || Windows 95|| 1996 || http://www.blizzard.com/  || http://www.blizzard.com/diablo/
 +
|-
 +
| SimCity || Sim || Interplay || Dos || 1993 || http://www.interplay.com/  || http://www.maxis.com/
 +
|}
 +
 
 +
Tables Games, Developers, Websites, Platforms?
  
−
        -- Insert statements for procedure here
+
Build Views
−
SELECT PeopleID FROM People WHERE firstName = @firstName AND lastName= @lastName AND logonName= @logonName
 
−
END
 
−
</sql>
 
  
−
Again we can runn it like this
+
==Nesting Data Bound Controls==
−
<sql>
+
nesting controls
−
GetPeopleID
 
−
@firstName ='sprocTestFname',
 
−
@lastName='sprocTestLname',
 
−
@logonName ='sprocTestLogonName'
 
−
</sql>
 
  
−
==Transactions==
+
Datasource Controls can probably handle up to 70% of your data binding needs but they do have drawbacks. Consider the cheese database which uses an SQL view to join Cheese with Region, Consistency, and MilkType. Of course SQL view don't support updating and can lead to some bad data binding. we can fix a few of these problem with stored procedures.
  
−
Whenever you are making changes (insert/update/delete) two more than one table or the results of a select statement are used to update another table you need to use a tracation.
+
Simple filter Demo in class
  
−
Locks
+
GridView Details View Master Child Relationship
  
−
Commit
 
  
−
Rollback
+
http://iam.colum.edu/dd/classsource/data/CheeseDataBindingFull.aspx
 +
[http://iam.colum.edu/dd/gbrowser.php?file=/classsource/Data/CheeseDataBindingFull1.aspx source]
  
 
==Stored Procedures==
 
==Stored Procedures==
  
−
===Fourth Normal Form===  
+
http://iam.colum.edu/dd/classsource/data/sproc/sprocADO.aspx
−
Fourth Normal Form
+
 
−
:separates independent multi-valued facts stored in one table into separate tables.
+
==Cheese browser assignment==
 +
 
 +
Make a creative cheese browser from that tables in you db. Use a view to join that data from multiple tables..
 +
 
 +
Here's and example of a simple cheese shop browser app.
 +
 
 +
http://iam.colum.edu/dd/classsource/class8/CheeseShop/CheeseShop1.aspx
 +
 
 +
==Homework==
 +
 
 +
Normalize these tables. Make a UML Drawing for both tables.
 +
 
 +
'''Games'''
 +
{| class="wikitable" cellpadding="5" cellspacing="0"
 +
!GameTitle !!  GameGenre !! DeveloperName !! Platform(s) !! Year !! DeveloperWebsite !! GameWebsite
 +
|-
 +
| Quake1 || FPS || id || Dos || 1996 || http://www.idsoftware.com/ || http://www.idsoftware.com/games/quake/quake/
 +
|-
 +
| Diablo|| RPG|| Blizzard || Windows 95|| 1996 || http://www.blizzard.com/  || http://www.blizzard.com/diablo/
 +
|-
 +
| SimCity || Sim || Interplay || Dos || 1993 || http://www.interplay.com/  || http://www.maxis.com/
 +
|}
 +
 
 +
'''Cheeses'''
 +
{| class="wikitable" cellpadding="5" cellspacing="0"
 +
!CheeseName !! CheeseDescription !! RegionName !! Consistency !! MilkType
 +
|-
 +
|Argentinian Reggianito || The vast grazing pastures of Argentina revealed themselves to be ideal for immigrant Italians.. || Hard || Argentina || Goats Milk
 +
|-
 +
| Feta || Feta is made in a traditional manner by a small family dairy in central Greece...
 +
|| Crumbly || Greek || Mix of Milks
 +
|-
 +
| Cheddar || The most widely purchased and eaten cheese in the world. Cheddar cheeses were originally made in England, however today they are manufactured in many countries all over the world. || Semi-Hard ||England || Cows Milk
 +
|}
 +
 
 +
Build a blog interface to the blog tables we built in class.
 +
The blog interface requires
 +
*An insert blog page. Don't worry about user names or authentications this is a very public blog more like a message board.
 +
*A blogroll display page. Be careful which control you use to display the data.
 +
 
 +
Extra Credit is an edit or delete page.
 +
 
 +
READ BDD Chapter 4 again Chapter 5
 +
 
 +
READ BAD Chapter 8
 +
 
 +
==Examples==
 +
http://iam.colum.edu/dd/classsource/Data/GridAndDetails.aspx
  
−
===Fifth Normal Form===
+
http://iam.colum.edu/dd/classsource/Data/GridDataBound.aspx
−
Fifth Normal Form
 
−
:breaks out data redundancy that is not covered by any of the previous normal forms.
 
  
−
==HomeWork==
+
http://iam.colum.edu/dd/classsource/Data/GridDetails.aspx
−
Course adder example
 
  
−
http://iam.colum.edu/dd/classsource/class8/student.aspx
+
http://iam.colum.edu/dd/classsource/Data/GridEdit.aspx
  
−
SQL Subquery
+
http://iam.colum.edu/dd/classsource/Data/GridSelect.aspx
  
−
<sql>SELECT CourseID, CourseName, CourseNumber
+
http://iam.colum.edu/dd/classsource/Data/GridSelectTheme.aspx
−
FROM Course
+
 
−
WHERE
+
http://iam.colum.edu/dd/classsource/Data/GridTemplate.aspx
−
(
 
−
  CourseID not in
 
−
  (
 
−
      SELECT CourseID FROM StudentsCourses_vw WHERE StudentID = @StudentID
 
−
  )
 
−
)
 
−
</sql>
 

Latest revision as of 03:40, 14 November 2011


Primary Keys

The candidate key selected as being most important for identifying a body of information (an entity, object or record).

Normalization

Normal Forms

First Normal

Form eliminates repeating groups by putting each into a separate table and connecting them with a one-to-many relationship.

Data Relationships

Not Following First Normal Form Repeating Groups

Blog1

BlogID BlogText recCreationDate Mood
1 Blog1 03/30/03 Happy
2 Blog2 03/30/03 Happy
3 Blog3 03/30/03 Sad
4 Blog4 03/30/03 Happy
5 Blog4 03/30/03 Mad

Tables that Follow First normal form

Blog2

BlogID BlogText recCreationDate MoodID
1 Blog1 03/30/03 1
2 Blog2 03/30/03 1
3 Blog3 03/30/03 2
4 Blog4 03/30/03 1
5 Blog4 03/30/03 3

Mood

MoodID MoodName
1 Happy
2 Sad
3 Mad
4 Afraid

1NF also

Removes multiple column with the same type of data

Books Not Normal

Books

Author Title_01 Pages_01 Title_02 Pages_02 Title_03 Pages_03
Michael Allen Dymmoch The Man Who Understood Cats 256 White Tiger 320
Joseph Cancellaro Exploring Sound Design for Interactive Media 272 
In Class Build Blogs Table and Normalize Books Table


http://en.wikipedia.org/wiki/First_normal_form

ERD

http://en.wikipedia.org/wiki/Entity-relationship_model

tools

Views

UserTest

UserID UserName LastLogon
1 jmeyers 3/30/03
2 bgates 4/1/03
3 sjobs 4/2/03
4 ltorvalds 4/3/03


EmailTest

EmailID UserID EmailAddress Active displayEmail
1 1 jeff@interactive.colum.edu 1 0
2 1 only_a_test@hotmail.com 0 0
3 2 bgates@microsoft.com 1 0

[INNER] JOIN

The INNER JOIN returns all rows from both tables where there is a match. If there are rows in User that do not have matches in Email, those rows will not be listed.

-- ANSI Style <sql> SELECT u.UserID, u.UserName, u.LastLogon, e.EmailAddress, e.active, e.displayEmail FROM UserTest u JOIN EmailTest e ON e.UserID = u.UserID </sql>

--Theta style <sql> SELECT u.UserID, u.UserName, u.LastLogon, e.EmailAddress, e.active, e.displayEmail FROM UserTest u, EmailTest e WHERE e.UserID = u.UserID </sql>

results 

UserID      UserName            LastLogon                     EmailAddress                     active displayEmail 
----------- ------------------- ----------------------------- -------------------------------- ------ ------------ 
1           jmeyers             2003-03-30 00:00:00.000       jeff@interactive.colum.edu       1      0
1           jmeyers             2003-03-30 00:00:00.000       only_a_test@hotmail.com          0      0
2           bgates              2003-04-01 00:00:00.000       bgates@microsoft.com             1      0

(3 row(s) affected)

LEFT [OUTER] JOIN

The LEFT JOIN returns all the rows from the first table (User), even if there are no matches in the second table (Email). If there are rows in User that do not have matches in Email, those rows also will be listed.

<sql> SELECT u.UserID, u.UserName, u.LastLogon, e.EmailAddress, e.active, e.displayEmail FROM UserTest u LEFT JOIN EmailTest e ON e.UserID = u.UserID </sql> 

UserID      UserName     LastLogon                 EmailAddress                 active displayEmail 
----------- ------------ ------------------------- ---------------------------- ------ ------------ 
1           jmeyers      2003-03-30 00:00:00.000   jeff@interactive.colum.edu   1      0
1           jmeyers      2003-03-30 00:00:00.000   only_a_test@hotmail.com      0      0
2           bgates       2003-04-01 00:00:00.000   bgates@microsoft.com         1      0
3           sjobs        2003-04-02 00:00:00.000   NULL                         NULL   NULL
4           ltorvalds    2003-04-03 00:00:00.000   NULL                         NULL   NULL

(5 row(s) affected)

RIGHT [OUTER] JOIN

The RIGHT JOIN returns all the rows from the second table (Email), even if there are no matches in the first table (User). If there had been any rows in Email that did not have matches in User, those rows also would have been listed.

<sql> SELECT u.UserID, u.UserName, u.LastLogon, e.EmailAddress, e.active, e.displayEmail FROM UserTest u RIGHT JOIN EmailTest e ON e.UserID = u.UserID </sql>

results 

UserID      UserName            LastLogon                     EmailAddress                     active displayEmail 
----------- ------------------- ----------------------------- -------------------------------- ------ ------------ 
1           jmeyers             2003-03-30 00:00:00.000       jeff@interactive.colum.edu       1      0
1           jmeyers             2003-03-30 00:00:00.000       only_a_test@hotmail.com          0      0
2           bgates              2003-04-01 00:00:00.000       bgates@microsoft.com             1      0

(3 row(s) affected)

Making views in enterprise manager is easy. Just add the tables you want to join and click. It does all the typing for you.


Review First Normal Form

Let build the example for the homework.

Build Interface to GameDB

Games

GameTitle GameGenre DeveloperName Platform(s) Year DeveloperWebsite GameWebsite
Quake1 FPS id Dos 1996 http://www.idsoftware.com/ http://www.idsoftware.com/games/quake/quake/
Diablo RPG Blizzard Windows 95 1996 http://www.blizzard.com/ http://www.blizzard.com/diablo/
SimCity Sim Interplay Dos 1993 http://www.interplay.com/ http://www.maxis.com/

Tables Games, Developers, Websites, Platforms?

Build Views

Nesting Data Bound Controls

nesting controls

Datasource Controls can probably handle up to 70% of your data binding needs but they do have drawbacks. Consider the cheese database which uses an SQL view to join Cheese with Region, Consistency, and MilkType. Of course SQL view don't support updating and can lead to some bad data binding. we can fix a few of these problem with stored procedures.

Simple filter Demo in class

GridView Details View Master Child Relationship


http://iam.colum.edu/dd/classsource/data/CheeseDataBindingFull.aspx source

Stored Procedures

http://iam.colum.edu/dd/classsource/data/sproc/sprocADO.aspx

Cheese browser assignment

Make a creative cheese browser from that tables in you db. Use a view to join that data from multiple tables..

Here's and example of a simple cheese shop browser app.

http://iam.colum.edu/dd/classsource/class8/CheeseShop/CheeseShop1.aspx

Homework

Normalize these tables. Make a UML Drawing for both tables.

Games

GameTitle GameGenre DeveloperName Platform(s) Year DeveloperWebsite GameWebsite
Quake1 FPS id Dos 1996 http://www.idsoftware.com/ http://www.idsoftware.com/games/quake/quake/
Diablo RPG Blizzard Windows 95 1996 http://www.blizzard.com/ http://www.blizzard.com/diablo/
SimCity Sim Interplay Dos 1993 http://www.interplay.com/ http://www.maxis.com/

Cheeses

CheeseName CheeseDescription RegionName Consistency MilkType
Argentinian Reggianito The vast grazing pastures of Argentina revealed themselves to be ideal for immigrant Italians.. Hard Argentina Goats Milk
Feta Feta is made in a traditional manner by a small family dairy in central Greece... Crumbly Greek Mix of Milks
Cheddar The most widely purchased and eaten cheese in the world. Cheddar cheeses were originally made in England, however today they are manufactured in many countries all over the world. Semi-Hard England Cows Milk

Build a blog interface to the blog tables we built in class. The blog interface requires

  • An insert blog page. Don't worry about user names or authentications this is a very public blog more like a message board.
  • A blogroll display page. Be careful which control you use to display the data.

Extra Credit is an edit or delete page.

READ BDD Chapter 4 again Chapter 5

READ BAD Chapter 8

Examples

http://iam.colum.edu/dd/classsource/Data/GridAndDetails.aspx

http://iam.colum.edu/dd/classsource/Data/GridDataBound.aspx

http://iam.colum.edu/dd/classsource/Data/GridDetails.aspx

http://iam.colum.edu/dd/classsource/Data/GridEdit.aspx

http://iam.colum.edu/dd/classsource/Data/GridSelect.aspx

http://iam.colum.edu/dd/classsource/Data/GridSelectTheme.aspx

http://iam.colum.edu/dd/classsource/Data/GridTemplate.aspx

Retrieved from "http://imamp.colum.edu/mediawiki/index.php?title=DD_Class10&oldid=20111"