Evolve
Flyway
Our great sponsors
Evolve | Flyway | |
---|---|---|
5 | 81 | |
824 | 7,763 | |
- | 1.0% | |
2.8 | 7.2 | |
10 days ago | 5 days ago | |
C# | Java | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Evolve
-
How to Handle MSSQL Database in CI/CD?
If you want to stay in C# land, look at Evolve.
-
Can I export database from PostgreSQL and connect it to my C# app?
So, in general, one would use a versioned database schema that would connect to a database and execute a series of SQL files. For C# you have things like Evolve.
-
The correct way to source control data
So you don't really source control the data, but you do source control the database schema. A common way in the .net world to do this is to use something like evolve which basically allows you to version SQL scripts and have them executed on application launch.
-
Best db migration tool options to use along with Entity Framework
Been using https://github.com/lecaillon/Evolve for many years. Its a .Net Core equivalent to Flyway. You run plain old SQL scripts and just follow a file naming convention. It can run embedded inside a project, it has a .Net Tool and a standalone CLI. The SQL scripts can also be embedded in the executable or as external files.
-
Developing with SQL Server in .NET
I've been using Evolve in the past, very simple and effective.
Flyway
-
Let's write a simple microservice in Clojure
The session logs show that the application loads configurations and establishes a connection with a PostgreSQL database. This involves initializing a HikariCP connection pool and Flyway for database migrations. The logs confirm that the database schema validation and migration checks were successful. The startup of the Jetty HTTP server follows, and the server becomes operational and ready to accept requests on the specified port.
-
Ask HN: What tool(s) do you use to code review and deploy SQL scripts?
Also RedGate, but Flyway has some reasons to recommend it over RedGate Deploy depending on your DBAs/workflows: https://flywaydb.org/
(Though I don't think it is "complete" or "perfect", either.)
EF Migrations are in a really good place now if you like/don't mind C# as a language (and you can easily embed SQL inside the C#, too, but there are benefits to being able to also run high level C# code). With today's tooling you can package your migration "runner application" as a single deployable executable for most platforms. You can build the executable once and run it in all your environments. (The same tool that updates your QA and Staging updates your Prod, testably running the same migrations.) Given the single executable deployable I might even consider using it for projects not themselves written in C#.
-
PostgreSQL Is Enough
There is a bit of tooling needed but is already around. For Java for example I had very good experience with a combination of flyway [1] for migrations, testcontainers [2] for making integration tests as easy as unit tests and querydsl [3] for a query and mapping layer.
[1] https://github.com/flyway/flyway
[2] https://java.testcontainers.org/modules/databases/postgres/
[3] https://github.com/querydsl/querydsl
-
Using Flyway to version your database
When software starts using a database, it's advisable to have version control, just as we have Github to control our source code. This is all to be sure about what was executed for that specific version. For Java and Spring boot, we have the Flyway framework that aims to resolve this situation, free of charge.
-
CI/CD for Databricks
If you're looking for tools, like https://www.liquibase.com/ or https://flywaydb.org/, which are database-state-based schema migration toolkits - it might be relatively straightforward to build similar ones using Databricks SQL drivers.
-
Working with jOOQ and Flyway using Testcontainers
Honestly I kind of wish there was a Lukas Eder database migration library. Call it whatever jooq-migration. At least I would have more insight of what is going on (<-- seriously look at the commit history).
-
Strategy to run database scripts on Kubernetes
This is a 4th option, which should play nice with ArgoCD. The following example runs flyway as a k8s job. The desired migration changes are recorded as files within the chart. This helm chart can be integrated with your application (Using hooks to determine when the migration job is run) or run manually.
-
How do your teams run DB migrations?
By using an opinionated framework within the app/service (like Flyway, Migrate, Diesel, etc). Schema migrations happen on app/service start-up.
-
I've never created a production database from scratch and am wondering how much trouble it would be to transition a one-to-one relationship to a one-to-many relationship if I determine at some point that the latter is required.
Depending on the language or platform there are libraries you can use to manage this, such as Prisma on node and Flyway for Java/JVM.
-
How should I document and/or automate schema changes?
It's probably overkill but I've used github plus flyway at a couple places in the past which is pretty nice tool for tracking changes to a variety of db's, it's also very helpful if you ever need to replicate a db in a new region/environment.
What are some alternatives?
Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
alembic - A database migrations tool for SQLAlchemy.
DbUp - DbUp is a .NET library that helps you to deploy changes to SQL Server databases. It tracks which SQL scripts have been run already, and runs the change scripts that are needed to get your database up to date.
HikariCP - 光 HikariCP・A solid, high-performance, JDBC connection pool at last.
Versioning.NET - A dotnet tool that automatically increments versions in csproj files based on git commit hints.
roundhouse - RoundhousE is a Database Migration Utility for .NET using sql files and versioning based on source control
H2 - H2 is an embeddable RDBMS written in Java.
AutoTrimps - AutoTrimps - Zek
dbmate - :rocket: A lightweight, framework-agnostic database migration tool.
sqlancer - Automated testing to find logic and performance bugs in database systems
Hibernate - Hibernate's core Object/Relational Mapping functionality