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
|
Hello, I'm trying to keep an "issue" per thread. This thread is related to an issue encountered and described in this post. During a migration I got an InvalidOperationException with the message "size is not meaningful for this data type.". Initially I thought that I'll get the same error when I execute the migration with "preview" enabled, however, I get yet another exception "The version table is not initialised correctly - it either does not exist or has no value." when executing it against an empty database. The preview feature doesn't feel like a logical way to "validate" the migration as it simply fails on the first error. Would it be possible for Lightspeed to provide the means for me to validate migrations and reports the obvious errors? With obvious, I mean errors that Lightspeed will raise during migration and not those that are specific to the underlying database engine. It would be great if those errors can be reported all at once in an ASP.NET or ASP.NET MVC or WPF application. Thanks, Werner |
|
|
|
|
The post is http://www.mindscapehq.com/forums/Post.aspx?ThreadID=4742&PostID=16918. For some reason, the editor created the hyperlink, but it doesn't work when you click on it. Werner |
|
|
|
|
Preview doesn't test or validate the migrations - it simply allows you to preview which migrations will be executed (for example to display a list to the user and ask for confirmation). That it fails when there is no version table is a bug - obviously this should preview the entire set of migrations (up to whatever target is specified if any). We'll try to get this fixed for you. I agree it would be useful if the preview could do a measure of validation - we'll take a look at whether this is feasible. It will certainly be limited in some ways (e.g. problems at the database level will only reveal themselves when run against a real database, and cross-migration analysis like doing an AddColumn when there is no corresponding AddTable would probably require more resources than we have available right now), but issues like inappropriate WithSize() should certainly be catchable. Thanks for the feedback! |
|
|
|
