| 9/28/2004 8:34:26 PM |
Are there any plans to incorporate the new features of ADO.NET (like SqlDependency and SqlNotificationRequest, etc) to the OR mapper. This would be extremely useful and a long awaited feature of SQL Server and ADO. Thanks.
-Joe |
| 9/29/2004 3:00:09 AM |
Hi Joe:
I will include support for generics, and most likely nullable types, but I do not plan on anything else from .NET v2.0 at the moment (although I'm willing to listen if there are some other good recommendations). I definitely do NOT plan on implementing anything that is specific to only MS SQL 2005 -- my mapper is designed to be the simplest O/R mapper available, making it easy to work with ANY database provider, but the flip-side of this is that I also only target the most common 80-90% usage scenarios -- other O/R mappers may fulfil more specific requirements on the high-end, along with added complexity.
Thanks, Paul Wilson |
| 9/29/2004 11:15:54 AM |
I can understand the notion of not being tied to MS.
Would we be allowed to modify the OR mapper code to include such features if we are targeting only SQL Server?
Thanks, Joe |
| 9/29/2004 5:32:46 PM |
Hi Joe:
It would certainly make perfect sense to do MS Sql specific things if that were all we were targetting. It would also probably make sense if I was trying to build a more complex mapper that could handle every case.
Anyhow, there is certainly nothing to prevent you from adding the feature yourself. If you do, and if you send it to me, I'll consider adding it if it doesn't break anything else, or require more work for those that don't want to use it -- and if I feel like its justified. Maybe others here could comment on what they think about this feature . . .
Thanks, Paul Wilson |