respawn

This post is mainly a reminder to myself when inevitably I forget what I was doing when designing Respawn. The general problem space is something I've covered quite a lot, but I haven't really walked through how Respawn works internally. The general problem is trying to find the correct order of deletion for tables when you have foreign key constraints. You can do something like: ALTER TABLE [Orders] NOCHECK CONSTRAINT [Read More]

Respawn, the intelligent database deleter, reached the 3.0 milestone today. In this release, Respawn now supports complex circular/cyclical relationships. When Respawn detects a cycle in the graph, it substitutes a separate deletion strategy by disabling/enabling foreign key constraints just for those tables affected. This release also adds support for Oracle, and drops support for SQL Server CE, bringing the supported databases to: SQL Server PostgreSQL MySQL/MariaDB [Read More]

Respawn, a small library designed to ease integration testing by intelligently clearing out test data, now supports .NET Core. Specifically, I now target: net45 netstandard1.2 netstandard2.0 I had waited quite a long time because I needed netstandard2.0 support for some SqlClient pieces. With those pieces in place, I can now support running Respawn on full .NET and .NET Core 1.x and 2.0 applications (and tests) [Read More]