﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on A developer perspective on SQL Server 2008</title><description>ET,
  
Sure there is a feature list, you just need to be CEO of Fortune 5 to do it, I think :-)
</description><link>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment7</link><guid>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment7</guid><pubDate>Fri, 15 Jun 2007 14:44:14 GMT</pubDate></item><item><title>ET commented on A developer perspective on SQL Server 2008</title><description>What I'd very much like to see in SQL Server is named sequences similiar to Oracle's. How difficult can that be? And it would save so much grief IDENTITY columns cause!
  
I wonder if there's some features request list we could vote on...
</description><link>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment6</link><guid>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment6</guid><pubDate>Fri, 15 Jun 2007 14:41:05 GMT</pubDate></item><item><title>Ayende Rahien commented on A developer perspective on SQL Server 2008</title><description>@Denis,
  
When it comes the time to use that, it would be easy to move it to the native 2008 support.
</description><link>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment5</link><guid>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment5</guid><pubDate>Sat, 09 Jun 2007 14:09:04 GMT</pubDate></item><item><title>Denis the SQL Menace commented on A developer perspective on SQL Server 2008</title><description>SQL Server 2008 has 2 new spatial data types built in
  
  
Nhibernate uses MsSqlSpatial which are Spatial Extensions for SQL Server 2005.
</description><link>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment4</link><guid>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment4</guid><pubDate>Sat, 09 Jun 2007 14:03:06 GMT</pubDate></item><item><title>Ayende Rahien commented on A developer perspective on SQL Server 2008</title><description>http://www.codeplex.com/NHibernateSpatial
</description><link>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment3</link><guid>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment3</guid><pubDate>Sat, 09 Jun 2007 13:59:48 GMT</pubDate></item><item><title>Denis the SQL Menace commented on A developer perspective on SQL Server 2008</title><description>What about Spatial Data, what is your opinion on that?
</description><link>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment2</link><guid>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment2</guid><pubDate>Sat, 09 Jun 2007 12:29:49 GMT</pubDate></item><item><title>pete w commented on A developer perspective on SQL Server 2008</title><description>Interesting... what if... our poco definitions were defined and managed by the database?
  
It would then be SQL Server's job to hydrate and persist objects, handle change managements, and automatically handle transactions, maybe bypass some of that marshalling between odbc and sql data reader?
  
  
My bet is that it would allow for tighter control of transactions, less I/O, and a higher control over your caching and loading considerations.
  
  
I wouldnt know where to begin on this one, but it seems as if the school of DDD could see some value in this idea.
  
Just wanted to bounce that off someone who could offer insight
  
-p
</description><link>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment1</link><guid>http://ayende.com/2502/a-developer-perspective-on-sql-server-2008#comment1</guid><pubDate>Wed, 06 Jun 2007 14:53:54 GMT</pubDate></item></channel></rss>