Keeping “historical” migrations in Django-south
After a system has gone through many migrations, and evolved enough for a second version, does it make sense to keep the old migrations around? I mean, old versions will use them to upgrade to the new one, sure, but should a fresh install have its database go through all the “historical” changes before arriving at the current shape? My gut feeling is that a fresh install should create the database “as it is”, not go through every mistake that was made in the product lifecycle until reaching a stable condition.
We are moving an Access based corporate front-end into a Web-based App [closed]
Closed 5 years ago.
statistics for checking imported data?
I’m working on a data migration of several hundred nodes from a Drupal 6 to a Drupal 7 site. I’ve got the data exported to the new site and I want to check it. Harkening back to my statistics classes, I recall that there is some way to figure out a random number of nodes to check to give me some percentage of confidence that the whole process was correct. Can anyone enlighten me as to this practical application of statistics? For any given number of units, how big must the sample be to have a given confidence interval?
Is it appropriate to run a complex enterprise-system configuration and migration project in a similar way to a Scrum development project?
I’m just starting out on the implementation of a large enterprise-wide system, which has complex requirements and many stakeholders.
TypeORM migration not generated in specified path using ormconfig.ts
I am using TypeORM with a ormconfig.ts file, and I am trying to generate a migration in a specific path using the following command:
TypeORM migration not generated in specified path using ormconfig.ts
I am using TypeORM with a ormconfig.ts file, and I am trying to generate a migration in a specific path using the following command:
How can I break my vendor lock-in situation?
I’m developing software for about 10 years. I began on QBasic and now I’m developing .NET using C# language. I’m always trying to follow the best design patterns and principals like SOLID. In short I’m very happy with my work while as a tiny ISV I’m free to choose between technologies. Of course we almost develop mid-size web applications for start-ups.
Re-engineering an ASP.NET AJAX project as ASP MVC
I have been asked to investigate the possibility of re-engineering an existing ASP.NET AJAX Web Application as under MVC.
Using Sql Server Change Data Capture with a frequently changing schema
We are looking into enabling Sql Server Change Data Capture for a new subsystem we are building.
Using Sql Server Change Data Capture with a frequently changing schema
We are looking into enabling Sql Server Change Data Capture for a new subsystem we are building.