<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://www.codeplex.com/rss.xsl"?><rss version="2.0"><channel><title>ChinookDatabase Work Item Rss Feed</title><link>http://www.codeplex.com/ChinookDatabase/WorkItem/List.aspx</link><description>ChinookDatabase Work Item Rss Description</description><item><title>Created Issue: Indexes based on primary keys should be UNIQUE</title><link>http://chinookdatabase.codeplex.com/WorkItem/View.aspx?WorkItemId=24257</link><description>If not, ORM tools like CodeSmith do not work as expected &amp;#40;as a non-unique index indicates that more rows will be returned per key&amp;#41;. I had planned to feature Chinook in a blog post, but this must be fixed for the following tables&amp;#47;indexes, before I can do that&amp;#58;&lt;br /&gt;&lt;br /&gt;CREATE INDEX IPK_Genre ON Genre&amp;#40;GenreId&amp;#41;&amp;#59;&lt;br /&gt;CREATE INDEX IPK_MediaType ON MediaType&amp;#40;MediaTypeId&amp;#41;&amp;#59;&lt;br /&gt;CREATE INDEX IPK_Artist ON Artist&amp;#40;ArtistId&amp;#41;&amp;#59;&lt;br /&gt;CREATE INDEX IPK_ProductItem ON Album&amp;#40;AlbumId&amp;#41;&amp;#59;&lt;br /&gt;CREATE INDEX IPK_Track ON Track&amp;#40;TrackId&amp;#41;&amp;#59;&lt;br /&gt;CREATE INDEX IPK_Employee ON Employee&amp;#40;EmployeeId&amp;#41;&amp;#59;&lt;br /&gt;CREATE INDEX IPK_Customer ON Customer&amp;#40;CustomerId&amp;#41;&amp;#59;&lt;br /&gt;CREATE INDEX IPK_Invoice ON Invoice&amp;#40;InvoiceId&amp;#41;&amp;#59;&lt;br /&gt;CREATE INDEX IPK_InvoiceLine ON InvoiceLine&amp;#40;InvoiceLineId&amp;#41;&amp;#59;&lt;br /&gt;CREATE INDEX IPK_Playlist ON Playlist&amp;#40;PlaylistId&amp;#41;&amp;#59;&lt;br /&gt;CREATE INDEX IPK_PlaylistTrack ON PlaylistTrack&amp;#40;PlaylistId&amp;#41;&amp;#59;&lt;br /&gt;&lt;br /&gt;should be&lt;br /&gt;&lt;br /&gt;CREATE UNIQUE INDEX IPK_Genre ON Genre&amp;#40;GenreId&amp;#41;&amp;#59;&lt;br /&gt;CREATE UNIQUE INDEX IPK_MediaType ON MediaType&amp;#40;MediaTypeId&amp;#41;&amp;#59;&lt;br /&gt;CREATE UNIQUE INDEX IPK_Artist ON Artist&amp;#40;ArtistId&amp;#41;&amp;#59;&lt;br /&gt;CREATE UNIQUE INDEX IPK_ProductItem ON Album&amp;#40;AlbumId&amp;#41;&amp;#59;&lt;br /&gt;CREATE UNIQUE INDEX IPK_Track ON Track&amp;#40;TrackId&amp;#41;&amp;#59;&lt;br /&gt;CREATE UNIQUE INDEX IPK_Employee ON Employee&amp;#40;EmployeeId&amp;#41;&amp;#59;&lt;br /&gt;CREATE UNIQUE INDEX IPK_Customer ON Customer&amp;#40;CustomerId&amp;#41;&amp;#59;&lt;br /&gt;CREATE UNIQUE INDEX IPK_Invoice ON Invoice&amp;#40;InvoiceId&amp;#41;&amp;#59;&lt;br /&gt;CREATE UNIQUE INDEX IPK_InvoiceLine ON InvoiceLine&amp;#40;InvoiceLineId&amp;#41;&amp;#59;&lt;br /&gt;CREATE UNIQUE INDEX IPK_Playlist ON Playlist&amp;#40;PlaylistId&amp;#41;&amp;#59;&lt;br /&gt;CREATE UNIQUE INDEX IPK_PlaylistTrack ON PlaylistTrack&amp;#40;PlaylistId&amp;#41;&amp;#59;&lt;br /&gt;&lt;br /&gt;Likewise, the enclosed chinook.sdf file needs to be recreated.&lt;br /&gt;</description><author>ErikEJ</author><pubDate>Mon, 10 Aug 2009 14:14:48 GMT</pubDate><guid isPermaLink="false">Created Issue: Indexes based on primary keys should be UNIQUE 20090810021448P</guid></item><item><title>Created Feature: Feature Request: Schema change to allow implementation of inheritance mapping strategies</title><link>http://chinookdatabase.codeplex.com/WorkItem/View.aspx?WorkItemId=22184</link><description>This request is from Rub member of the uNhAddIns project &amp;#40;Unofficial addins for NHibernate&amp;#41;&amp;#58; http&amp;#58;&amp;#47;&amp;#47;code.google.com&amp;#47;p&amp;#47;unhaddins&amp;#47;&lt;br /&gt;&lt;br /&gt;Change the schema to allow developers to implement the three basic strategies for inheritance mapping&amp;#58;&lt;br /&gt;&lt;br /&gt;1. Table per Class Hierarchy&lt;br /&gt;2. Table per Subclass&lt;br /&gt;3. Table per Concrete Class&lt;br /&gt;&lt;br /&gt;For more info, see&amp;#58;&lt;br /&gt;http&amp;#58;&amp;#47;&amp;#47;www.nhforge.org&amp;#47;doc&amp;#47;nh&amp;#47;en&amp;#47;index.html&amp;#35;inheritance&lt;br /&gt;</description><author>lerocha</author><pubDate>Sun, 26 Apr 2009 22:30:24 GMT</pubDate><guid isPermaLink="false">Created Feature: Feature Request: Schema change to allow implementation of inheritance mapping strategies 20090426103024P</guid></item><item><title>Created Feature: Support for NHibernate using HiLo generator</title><link>http://chinookdatabase.codeplex.com/WorkItem/View.aspx?WorkItemId=22115</link><description>This request is from Rub member of the uNhAddIns project &amp;#40;Unofficial addins for NHibernate&amp;#41;&amp;#58; http&amp;#58;&amp;#47;&amp;#47;code.google.com&amp;#47;p&amp;#47;unhaddins&amp;#47;&lt;br /&gt;&lt;br /&gt;The current scripts use Identity to auto-generate primary keys. Although NHibernate supports Identity, it is not a good solution for it, as described below&amp;#58;&lt;br /&gt;http&amp;#58;&amp;#47;&amp;#47;nhforge.org&amp;#47;blogs&amp;#47;nhibernate&amp;#47;archive&amp;#47;2008&amp;#47;12&amp;#47;21&amp;#47;identity-the-never-ending-story.aspx&lt;br /&gt;&lt;br /&gt;We need to add support for nhibernate HiLo generation. For example, the Genre table would be&amp;#58;&lt;br /&gt;&lt;br /&gt;CREATE TABLE Genre &lt;br /&gt;&amp;#40; &lt;br /&gt;    GenreId INTEGER NOT NULL, &amp;#47;&amp;#47;  IDENTITY - no identity  here &lt;br /&gt;    Name NVARCHAR&amp;#40;120&amp;#41;,&lt;br /&gt;    PRIMARY KEY&amp;#40;GenreId&amp;#41;&lt;br /&gt;&amp;#41;&amp;#59;&lt;br /&gt;</description><author>lerocha</author><pubDate>Mon, 20 Apr 2009 05:15:15 GMT</pubDate><guid isPermaLink="false">Created Feature: Support for NHibernate using HiLo generator 20090420051515A</guid></item><item><title>Created Feature: Feature Request</title><link>http://chinookdatabase.codeplex.com/WorkItem/View.aspx?WorkItemId=22114</link><description>Feature requests by Evoluteur&amp;#58;&lt;br /&gt;- script to drop all tables &amp;#40;because it needs to drop ref integrity first&amp;#41;.&lt;br /&gt;- triggers to update order total.&lt;br /&gt;- a few records in Chinese or Japanese&lt;br /&gt;</description><author>lerocha</author><pubDate>Mon, 20 Apr 2009 04:55:25 GMT</pubDate><guid isPermaLink="false">Created Feature: Feature Request 20090420045525A</guid></item><item><title>Closed Issue: Error when creating database for the first time in SQL Server Express</title><link>http://www.codeplex.com/ChinookDatabase/WorkItem/View.aspx?WorkItemId=20453</link><description>When trying to create the Chinook Database for the first time &amp;#40;SQL Express only&amp;#41; we get the following error&amp;#58;&lt;br /&gt;&lt;br /&gt;Msg 911, Level 16, State 1, Server VM-MCPD&amp;#92;SQLEXPRESS, Line 13&lt;br /&gt;Could not locate entry in sysdatabases for database &amp;#39;Chinook&amp;#39;. No entry found with that name. Make sure that the name is entered correctly.&lt;br /&gt;&lt;br /&gt;The scripts for the other databases do not have this issue.&lt;br /&gt;&lt;br /&gt;Workaround&amp;#58;&lt;br /&gt;Edit the Scripts&amp;#92;SqlServer&amp;#92;CreateDB.sql and add the GO command line right after the CREATE DATABASE line&amp;#58;&lt;br /&gt;&lt;br /&gt;IF EXISTS &amp;#40;SELECT name FROM master.dbo.sysdatabases WHERE name &amp;#61; N&amp;#39;Chinook&amp;#39;&amp;#41; DROP DATABASE &amp;#91;Chinook&amp;#93;&amp;#59;&lt;br /&gt;CREATE DATABASE &amp;#91;Chinook&amp;#93;&amp;#59;&lt;br /&gt;GO&lt;br /&gt;</description><author>lerocha</author><pubDate>Tue, 06 Jan 2009 03:00:44 GMT</pubDate><guid isPermaLink="false">Closed Issue: Error when creating database for the first time in SQL Server Express 20090106030044A</guid></item><item><title>Created Issue: Error when creating database using SQL Express 2005</title><link>http://www.codeplex.com/ChinookDatabase/WorkItem/View.aspx?WorkItemId=20453</link><description>When trying to create the Chinook Database using SQL Express 2005 we get the following error&amp;#58;&lt;br /&gt;&lt;br /&gt;Msg 911, Level 16, State 1, Server VM-MCPD&amp;#92;SQLEXPRESS, Line 13&lt;br /&gt;Could not locate entry in sysdatabases for database &amp;#39;Chinook&amp;#39;. No entry found with that name. Make sure that the name is entered correctly.&lt;br /&gt;&lt;br /&gt;This only happens when&amp;#58;&lt;br /&gt;1. Using SQL Express 2005.&lt;br /&gt;2. It is the first time that the Chinook Database is created on the DB Server.&lt;br /&gt;&lt;br /&gt;Workaround&amp;#58;&lt;br /&gt;Edit the Scripts&amp;#92;SqlServer&amp;#92;CreateDB.sql and add the GO command line right after the CREATE DATABASE line&amp;#58;&lt;br /&gt;&lt;br /&gt;IF EXISTS &amp;#40;SELECT name FROM master.dbo.sysdatabases WHERE name &amp;#61; N&amp;#39;Chinook&amp;#39;&amp;#41; DROP DATABASE &amp;#91;Chinook&amp;#93;&amp;#59;&lt;br /&gt;CREATE DATABASE &amp;#91;Chinook&amp;#93;&amp;#59;&lt;br /&gt;GO&lt;br /&gt;</description><author>lerocha</author><pubDate>Mon, 05 Jan 2009 21:30:12 GMT</pubDate><guid isPermaLink="false">Created Issue: Error when creating database using SQL Express 2005 20090105093012P</guid></item><item><title>Closed Task: Change Chinook database schema representation</title><link>http://www.codeplex.com/ChinookDatabase/WorkItem/View.aspx?WorkItemId=20380</link><description>The Chinook schema database is represented by a DataSet schema, which is used by T4 templates to generate the SQL scripts.&lt;br /&gt;&lt;br /&gt;Investigate if it is feasible to use a newer representation &amp;#40;dbml or edmx&amp;#41; instead, and if so, convert the current schema and update the T4 templates.&lt;br /&gt;</description><author>lerocha</author><pubDate>Mon, 05 Jan 2009 04:03:34 GMT</pubDate><guid isPermaLink="false">Closed Task: Change Chinook database schema representation 20090105040334A</guid></item><item><title>Closed Task: Need to create additional sample data for customers</title><link>http://www.codeplex.com/ChinookDatabase/WorkItem/View.aspx?WorkItemId=20381</link><description>Create additional sample data for the customers table.&lt;br /&gt;&lt;br /&gt;Need to use Customers from different countries and use valid address that will correctly appear in Google maps.&lt;br /&gt;</description><author>lerocha</author><pubDate>Sun, 04 Jan 2009 08:07:12 GMT</pubDate><guid isPermaLink="false">Closed Task: Need to create additional sample data for customers 20090104080712A</guid></item><item><title>Closed Task: Add support for SQL Server Compact</title><link>http://www.codeplex.com/ChinookDatabase/WorkItem/View.aspx?WorkItemId=20383</link><description>One of our users sent a script for SQL Server Compact. We need to update the T4 templates in order to also generate this script.&lt;br /&gt;</description><author>lerocha</author><pubDate>Tue, 30 Dec 2008 05:25:16 GMT</pubDate><guid isPermaLink="false">Closed Task: Add support for SQL Server Compact 20081230052516A</guid></item><item><title>Closed Task: Change version number to 1.1</title><link>http://www.codeplex.com/ChinookDatabase/WorkItem/View.aspx?WorkItemId=20385</link><description>Need to change the scripts version number to 1.1 in DataSetHelper.tt before the main release.&lt;br /&gt;</description><author>lerocha</author><pubDate>Mon, 29 Dec 2008 07:51:32 GMT</pubDate><guid isPermaLink="false">Closed Task: Change version number to 1.1 20081229075132A</guid></item><item><title>Closed Task: Add a many-to-many relationship to the schema</title><link>http://www.codeplex.com/ChinookDatabase/WorkItem/View.aspx?WorkItemId=20382</link><description>There is no many-to-many relationship in the current schema. Although we want to keep this schema as simple as possible, we still want to provide at least one many-to-many relationship.&lt;br /&gt;&lt;br /&gt;Suggestion&amp;#58; Create a new entity Playlist which has a many-to-many relationship with the Track entity. This will result in two new tables&amp;#58; Playlist and PlaylistTrack tables.&lt;br /&gt;</description><author>lerocha</author><pubDate>Mon, 29 Dec 2008 07:51:31 GMT</pubDate><guid isPermaLink="false">Closed Task: Add a many-to-many relationship to the schema 20081229075131A</guid></item><item><title>Created Task: Change version number to 1.1</title><link>http://www.codeplex.com/ChinookDatabase/WorkItem/View.aspx?WorkItemId=20385</link><description>Need to change the scripts version number to 1.1 in DataSetHelper.tt before the main release.&lt;br /&gt;</description><author>lerocha</author><pubDate>Sat, 27 Dec 2008 23:23:08 GMT</pubDate><guid isPermaLink="false">Created Task: Change version number to 1.1 20081227112308P</guid></item><item><title>Created Task: Add support for SQL Server Compact</title><link>http://www.codeplex.com/ChinookDatabase/WorkItem/View.aspx?WorkItemId=20383</link><description>One of our users sent a script for SQL Server Compact. We need to update the T4 templates in order to also generate this script.&lt;br /&gt;</description><author>lerocha</author><pubDate>Sat, 27 Dec 2008 22:14:03 GMT</pubDate><guid isPermaLink="false">Created Task: Add support for SQL Server Compact 20081227101403P</guid></item><item><title>Created Task: Add a many-to-many relationship to the schema</title><link>http://www.codeplex.com/ChinookDatabase/WorkItem/View.aspx?WorkItemId=20382</link><description>There is no many-to-many relationship in the current schema. Although we want to keep this schema as simple as possible, we still want to provide at least one many-to-many relationship.&lt;br /&gt;&lt;br /&gt;Suggestion&amp;#58; Create a new entity Playlist which has a many-to-many relationship with the Track entity. This will result in two new tables&amp;#58; Playlist and PlaylistTrack tables.&lt;br /&gt;</description><author>lerocha</author><pubDate>Sat, 27 Dec 2008 22:11:09 GMT</pubDate><guid isPermaLink="false">Created Task: Add a many-to-many relationship to the schema 20081227101109P</guid></item><item><title>Created Task: Need to create additional sample data for customers</title><link>http://www.codeplex.com/ChinookDatabase/WorkItem/View.aspx?WorkItemId=20381</link><description>Create additional sample data for the customers table.&lt;br /&gt;&lt;br /&gt;Need to use Customers from different countries and use valid address that will correctly appear in Google maps.&lt;br /&gt;</description><author>lerocha</author><pubDate>Sat, 27 Dec 2008 21:59:39 GMT</pubDate><guid isPermaLink="false">Created Task: Need to create additional sample data for customers 20081227095939P</guid></item><item><title>Created Task: Change Chinook database schema representation</title><link>http://www.codeplex.com/ChinookDatabase/WorkItem/View.aspx?WorkItemId=20380</link><description>The Chinook schema database is represented by a DataSet schema, which is used by T4 templates to generate the SQL scripts.&lt;br /&gt;&lt;br /&gt;Investigate if it is feasible to use a newer representation &amp;#40;dbml or edmx&amp;#41; instead, and if so, convert the current schema and update the T4 templates.&lt;br /&gt;</description><author>lerocha</author><pubDate>Sat, 27 Dec 2008 21:54:38 GMT</pubDate><guid isPermaLink="false">Created Task: Change Chinook database schema representation 20081227095438P</guid></item></channel></rss>