Adding a (not null) column problem
Brian Donahue
Posts: 6,590 Bronze 1
Hi Trevor,
No through SQL Compae, no. It's a good practice to specify a default for
columns that do not accept NULLs. I've learned this the 'hard way', and now
I stop and think about it during my own database design process. It's a good
idea not only for when you make schema changes, but also if you import data
from other sources.
Regards,
Brian Donahue
Red Gate Technical Support
"Trevor Best" <no@spam.com> wrote in message
news:prgm7G%237DHA.2540@server53...
> If I add a column that is not null to a database then synchronising
> fails, as you'd expect. I got the column on there in the first instance
> by adding a default value so that EM would populate it, I then take the
> default value off.
>
> Is there an easy way around this problem in synchronising?
>
No through SQL Compae, no. It's a good practice to specify a default for
columns that do not accept NULLs. I've learned this the 'hard way', and now
I stop and think about it during my own database design process. It's a good
idea not only for when you make schema changes, but also if you import data
from other sources.
Regards,
Brian Donahue
Red Gate Technical Support
"Trevor Best" <no@spam.com> wrote in message
news:prgm7G%237DHA.2540@server53...
> If I add a column that is not null to a database then synchronising
> fails, as you'd expect. I got the column on there in the first instance
> by adding a default value so that EM would populate it, I then take the
> default value off.
>
> Is there an easy way around this problem in synchronising?
>
This discussion has been closed.
