The problem is that I need the update with the alter of each column to add with "not null" constraint if the mapping specify this.
On Mon, Jun 20, 2011 at 6:48 PM, Ayende Rahien <[email protected]> wrote: > 5. There is a null value there, what is going on now? > > > On Mon, Jun 20, 2011 at 5:41 PM, Matteo Migliore < > [email protected]> wrote: > >> Hi! >> >> I would use SchemaUpdate to launch migration scripts but is known that the >> null constraint is "turned off". >> >> How is possible to apply a "strict" version of the update script? >> I've a mechanism to fill with valid data the not nullable columns so my >> steps should be: >> 1. disable all DB constraints >> 2. launch the create/alter scripts >> 3. launch my "data filler" >> 4. enable all DB constraints >> >> Thanks! > > >
