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
|
LightSpeed 5.0.3066.0 When I try to add a uniqueness validation on a column in a migration, the following code is generated: Unfortunately, when executed against Oracle database it results in |
|
|
|
|
This looks like an issue in that we fully specify the column definition and Oracle doesnt like it when you define the nullability in the ALTER TABLE statement where it matches the existing definition. It looks like you will need to use an ExecuteNativeCommand specifying the SQL associated with this removing the nullability aspect as a workaround here.
|
|
|
|
