<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Open Coding &#187; SQL</title>
	<atom:link href="http://code.dortikum.net/category/sql/feed/" rel="self" type="application/rss+xml" />
	<link>http://code.dortikum.net</link>
	<description>Free your imagination</description>
	<lastBuildDate>Wed, 28 Jul 2010 12:45:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Untie the Connection String from DataContext (LINQ to SQL)</title>
		<link>http://code.dortikum.net/2009/11/27/untie-the-connection-string-from-datacontext-linq-to-sql/</link>
		<comments>http://code.dortikum.net/2009/11/27/untie-the-connection-string-from-datacontext-linq-to-sql/#comments</comments>
		<pubDate>Fri, 27 Nov 2009 20:50:25 +0000</pubDate>
		<dc:creator>Boyan Mihaylov</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[ADO.NET]]></category>
		<category><![CDATA[C#]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[conection string]]></category>
		<category><![CDATA[datacontext]]></category>
		<category><![CDATA[linq to sql]]></category>

		<guid isPermaLink="false">http://code.dortikum.net/?p=174</guid>
		<description><![CDATA[When you work with LINQ to SQL you probably want your DataContext (and all the entities) to be in its own assembly. It&#8217;s a normal decision when developing n-tier applications. The Problem When you create your LINQ to SQL classes file (dbml) you have two options for your database connection string: In Settings.settngs file of the [...]]]></description>
		<wfw:commentRss>http://code.dortikum.net/2009/11/27/untie-the-connection-string-from-datacontext-linq-to-sql/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mapping a Stored Procedure to an Entity with Entity Framework</title>
		<link>http://code.dortikum.net/2009/11/23/mapping-a-stored-procedure-to-an-entity-with-entity-framework/</link>
		<comments>http://code.dortikum.net/2009/11/23/mapping-a-stored-procedure-to-an-entity-with-entity-framework/#comments</comments>
		<pubDate>Mon, 23 Nov 2009 18:54:49 +0000</pubDate>
		<dc:creator>Boyan Mihaylov</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[ADO.NET]]></category>
		<category><![CDATA[C#]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[entity framework]]></category>
		<category><![CDATA[orm]]></category>
		<category><![CDATA[stored procedure]]></category>

		<guid isPermaLink="false">http://code.dortikum.net/?p=162</guid>
		<description><![CDATA[ADO.NET Entity Framework initially generates a 1:1 (one to one) mapping between the database schema and the conceptual schema in most of the cases. In the relational schema, the elements are composed of the tables, with the primary and foreign keys gluing the related tables together. In contrast, the Entity Types define the conceptual schema [...]]]></description>
		<wfw:commentRss>http://code.dortikum.net/2009/11/23/mapping-a-stored-procedure-to-an-entity-with-entity-framework/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
