This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Any updates or plans on SQL 2008 DateTime2 support? We use that a lot because it maps directly to the BCL's DateTime, the full 0001 to 9999. (We've found zero use for the other date/time types, and just use longs for TimeSpans (ticks) -- Linq-to-Sql actually supports that directly too.) Thanks, Michael |
|
|
|
|
Hi Michael, Yes - we are intending to support all of the new SQL2008 data types are part of our LightSpeed 3.0 release where we will be introducing a new more specific provider for SQL2008 :) Currently we are looking at mid year for the release of 3.0 - as previously we are likely to get a beta program out in advance of this release so if you are interested you could look at using some of the earlier bits if this would fit in with your current development.
Jeremy |
|
|
|
|
Quick follow up to this - we have looked quickly this morning at adding in some quick support for DateTime2 since it seemed like a nice one to support ASAP. I have added in new SqlServer2008 provider which will handle the DateTime2 parameters and this will be available to try out in the next nightly build :) To use this, just make sure you set your DataProvider to be SqlServer2008 and you should be away. Would appreciate your feedback on this.
Jeremy
|
|
|
|
|
I'll try to refrain from using profanity! I am what you would call "duly impressed", to understate it. Well, I'm definately going to give LightSpeed a more in-depth review. After spending too much time reading and comparing ORMs, LightSpeed is definately the most slick product I have seen. The problem is that I think LightSpeed might not be flexible enough overall for the particular project I have in mind (on a fresh new project, these objections might be irrelevant). I love convention-over-configuration for most cases. (Just thinking about all the work I'd have to do with NHibernate makes me wince.) But, I think I might need that configuration for some areas. Like custom mapping data types, composite keys, etc. I'll start another thread once I have more definite questions. Thanks, Michael |
|
|
|
