Is NHibernate SchemaUpdate safe in production code? -


for simplicity's sake. i'm using fluent nhibernate's automapping combined nhibernate's schemaupdate during runtime. on each run automapper creates mappings entity classes , schemaupdate applies schema existing database. pleasantly surprised works correctly against empty database well. it's worked fine far in development environment , has allowed me respond bugs rather quickly.

my question whether reliable enough leave in production code. doesn't need run every time program starts in production environment useful incremental product updates (though don't plan on making major changes domain after product ships).

(perhaps real question should how safe use these 2 tools in conjunction?)

update

the application has 2 versions: standalone desktop , multiuser client/server. due nature of business domain (tax software) have luxury of starting clean database each year.

for able run in production code, account production application uses connect database have have permission change database schema.

that alone should deter approach, irrespective of quality/reliability of nhibernate code.


Comments

Popular posts from this blog

unicode - Are email addresses allowed to contain non-alphanumeric characters? -

C#: Application without a window or taskbar item (background app) that can still use Console.WriteLine() -

c++ - Convert big endian to little endian when reading from a binary file -