Function is not created first when used as default value

We've noticed with Sql Compare (and the SQL Comparison SDK) that it doesn't realise it needs to create a FUNCTION first if that function is used as a DEFAULT value for a TABLE definition.

Is this a known issue, and has it been corrected in a more recent version?



Sign In or Register to comment.