Questions about NH usage belong in the nhusers group. Anyway, the schema classes are not a migrations framework. They are intended to be used during development only and will not preserve dat.
On Wed, May 22, 2013 at 9:05 PM, <[email protected]> wrote: > Hi All, > > I ran a few tests with the code first generation of tables. Seems to work > fine. I load some data into the tables and then add a few more columns to > one of my tables ala code first. When I regenerate the schema, it adds the > columns just fine. The problem is that the table with the new columns is > now empty. It appears that the schema generation process is dropping the > table and recreating it. Is there a flag or switch that can be used to > issue an Alter statement instead of a drop? Is this even possible with NH? > Or is this something outside of the original intent of the code first > implementation? > > Thanks in advance. > Felix > > -- > > --- > You received this message because you are subscribed to the Google Groups > "nhibernate-development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
