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
|
Hi! Sorry to bother you more, but just found one issue with Oracle. Columns of TIMESTAMP type end up as Object properties in the Designer generated classes. We do need timestamps as our SW tracks and logs production process so we sometimes need more than 1 second precision. I also noticed that BINARY_FLOAT and BINARY_DOUBLE end up as Object too. Both are actually Oracle implementations of IEEE floating point values, so they should really fit naturally to float (Single) and double in .NET |
|
|
|
|
I've added these types and they will be supported by the designer in nightly builds dated 31 July 2009 and above. Note that this does not change the behaviour for model-first design, only for database-first (dragging tables on or using Update From Source). Also I have noticed some problems with using these data types with the Microsoft Oracle client: I assume you are using ODP.NET but I thought I'd mention it in case anybody else tries to use them with the Microsoft provider. This is not a LightSpeed issue but an ADO.NET issue. |
|
|
|
|
Thanks Ivan! Since you brought that up, not sure you've heard that Microsoft will be droping their ADO.NET Oracle client System.Data.Oracleclient. In framework 4.0 it will be marked as deprecated. So this probably also means no Entity Framework for Oracle from MS. And Oracle is still ignoring EF. Third party solutions are still the only way for LINQ on Oracle. Looks to me like there is a giants war out there, but I think you'll probably (I hope) have some benefit from it.
|
|
|
|
|
I've tried this, and the designer is pick-ing up new types correcty. |
|
|
|
