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, During a migration I got an InvalidOperationException with the message "size is not meaningful for this data type.". The problem is the migration is rather large (40+ tables) and I find it nearly impossible to determine which field of which table has a size which isn't meaningful. Can Lightspeed provide more context with its error error message, like one that describe exactly what is wrong with which field in which table? This will simplify troubleshooting a great deal. Thanks, Werner
|
|
|
|
|
Done and will be in next nightly build. For the time being we are only able to report the field name, not the table name, but that should cut it down quite a bit (and the error location should definitely make it clear which table is involved). |
|
|
|
|
Hi Ivan, To reproduce, create an entity with a string field. Then add a length validation of say "<= 128" to the field. Now change that string field to be of type Int32. Generate the migration. It seems Lightspeed is incorrectly generating a WithSize method for the Int32 field. My expectation would be that the length validation be ignored since its a primitive type that has a fixed length. Alternatively, the designer could hide the validate length field when you change it to a type that doesn't support lengths. I hope this makes sense. Werner |
|
|
|
