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
|
I've created a user defined type SqlGeography : CLR TypeName : Microsoft.SqlServer.Types.SqlGeography ConverterType : [emtpy] Database Type Name : geography Is Standard Data Type : false Is Value Type : false Name : SqlGeography I've created a migration and the table containing that type generated a line like this : When I run the migration from the IDE, I get a message saying there's an operand clash between int and sqlgeography. However, when I update the db via "Update database" option from the Designer's context menu - everything works fine. What's wrong? Please note, that I'm using SqlServer2012 Express |
|
|
|
|
Thanks for reporting this - I have found an issue with how the migrations were handling UDT's when it came to applying them for updates in that it would incorrectly append a DEFAULT 0 when they were set as non nullable. I have added in a fix for this and this will be available in tonights nightly build. Let me know if you continue to have any issues with this. As an aside, you know that SqlGeography is actually already directly handled by LightSpeed if you are using the SqlServer 2008 provider? So you shouldnt actually need to define a specific UDT for this data type :)
|
|
|
|
|
Speaking of the forementioned provider, I'm not seeing SqlServer2008 in some places - for instance when I click on designer's background and select it's properties - I'm seeing SqlServer & SqlServer 2005 but no 2008 - other places are subject to this as well - is it intended? |
|
|
|
|
Yes, that is correct - within the Designer environment we only have SqlServer2005 listed which is used to cover 2005 and 2008+R2. If you are using that option in the Designer it will handle the 2008 types but you need to specify the SqlServer2008 provider for runtime.
|
|
|
|
