bytebase
migrate
bytebase | migrate | |
---|---|---|
36 | 72 | |
10,107 | 14,000 | |
2.9% | 2.0% | |
10.0 | 8.0 | |
3 days ago | 12 days ago | |
Go | Go | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
bytebase
-
Ask HN: What tool(s) do you use to code review and deploy SQL scripts?
We have been building https://github.com/bytebase/bytebase for 3+ years. You can think it of as GitHub/GitLab for SQL changes, with integrated GitOps, code review and deployment.
You can further check out this tutorial to get a feel of our GitOps solution
https://www.bytebase.com/docs/tutorials/database-change-mana...
-
Resend – Incident report for February 21st, 2024
We have been working on bytebase (https://github.com/bytebase/bytebase) for 3+ years to address this. With a change review workflow, environment propagations, and try not to disturb the dev flow if possible.
-
PostgreSQL Is Enough
Migrations. All my database logic lives in version control.
Popular tooling like Phoenix, Hasura, etc have good built in migration stories.
https://www.bytebase.com looks really promising.
Hover, I do struggle with one big issue: changing database logic (views, functions, etc) that has other logic dependent on it. This seems like a solvable problem.
-
A list of SaaS, PaaS and IaaS offerings that have free tiers of interest to devops and infradev
bytebase.com — Database CI/CD and DevOps. Free under 20 users and ten database instances
-
🚛 Deploy Database Schema Migrations with Bytebase
Bytebase offers a powerful GUI for schema migration deployments. This tutorial will show you how to use Bytebase to deploy schema migrations with features like SQL Review, custom approval, time scheduling, and more.
- Bytebase – The Only Database CI/CD Workspace
-
Are "Infrastructure as Code" limited to "Infrastructure" only?
Now there are more subdivided practice: * Policy as Code: Sentinel, OPA * Database as Code: bytebase * AppConfiguration as Code: KusionStack, Acorn * ...... (Welcome to add more)
-
🐬Top 5 MySQL GUI Clients to Command MySQL⚡️
Bytebase is an open-source Database DevOps and CI/CD tool for teams, designed to centralize the control and secure your organization’s most valuable asset, the database data.
-
database changes tracking tools
I use Bytebase to manage database changes for MySQL with GitOps workflow. I can manage my SQL scripts in my GitLab repo, and trigger a database change issue with committing a MR. Then Bytebase will record it after the issue is executed successfully. But I am not sure whether it supports procedures. Refer to https://github.com/bytebase/bytebase to get more details.
- Version control for database used by C# app
migrate
-
Using migrations with Golang
Go does not natively support the use of migrations, but we could use the ORM that has this functionality, such as GORM which is the most used by the community, but We can use migrations without using an ORM, for this we will use the golang-migrate package.
-
How to use SQLC with Golang
$ curl -L https://github.com/golang-migrate/migrate/releases/download/$version/migrate.$os-$arch.tar.gz | tar xvz
- Looking for recommendations for model/schema/migration management in Golang
- API completa em Golang - Parte 1
-
Building RESTful API with Hexagonal Architecture in Go
Golang-migrate is a database migration tool designed for Go applications. It helps manage and apply changes to the database schema as the application grows, ensuring that the code and database structure stay in sync.
-
Python: Just Write SQL
First of all, thank you for SQLAlchemy! If I ever had to make a final choice in how I would interact with a database for a very large project that involves a considerable dev team, I would always bet on SQLAlchemy. Not that I would necessarily like all aspects of it, but when it comes to Python and SQL - “Nobody ever got fired for picking SQLAlchemy.”.
With that out of the way, despite ORMs doing much more than "just writing SQL", it is exactly on that point that I flinch: Most devs should be exposed to SQL. And if your project allows you to build around simple enough abstractions so that you aren't reinventing the wheel, you should definitely be writing SQL. Especially if you don't know SQL yet - which is the growing case of new devs coming into the job market.
You can achieve a lot with SQlAlchemy Core, a tool that I absolutely recommend, but my post is just a simple alternative to get developers to think about their approach. If that results in some devs reconsidering using "full fat" SQLAlchemy and to try SQLAlchemy Core, that's a win for me!
Your gist tries to highlight the difficulty of doing certain things without an ORM. Migrations (as just 1 example) doesn't need to be hard, simple tools like flyway, or migrate (https://github.com/golang-migrate/migrate) achieve a similar result (while also keeping you on the path of writing SQL!). Deep and complex relationships between objects also don't need to be hard - typically people approach this subject with a requirement to be very flexible in the way they want to build queries and objects, but that to me in a sign that maybe they should reconsider their business logic AND reconsider that, just maybe, their project doesn't require all that flexibility, it is fairly straightforward to extend objects and introduce some more complex representations as and when it is needed - will all of this make me write code faster? Absolutely not. That is why you have spent so much time perfecting SQLAlchemy, but then again, I am not advocating for devs to go and replace their usage of ORMs, just presenting an alternative that may or may not fit their needs for a new project + give devs the chance to learn something that the ORM might have taken away.
-
best practices for testing of stored procedure calls?
Doing this now with a mysql db for my use case. Using sp to take a large chunk of data migration load off my data layer code. I am using migrate (go library) for migrations and hooked it up with a bunch of test suites for all SP and Triggers it creates. I test it against a testDB maintained as part of my CI/CD. Haven’t had an issue with production yet. It does however require quite a bit of initial setup.
- Database migration tool
-
REST API with Go, Chi, MySQL and sqlx
Before we can start using MySQL we need to create a table to store our data. I will be using excellent migrate database migrations tool, it can also be imported as a libraray.
-
Authentication system using Golang and Sveltekit - User registration
We need a database table to store our application's users' data. To generate and migrate a schema, we'll use golang migrate. Kindly follow these instructions to install it on your Operating system. To create a pair of migration files (up and down) for our user table, issue the following command in your terminal and at the root of your project:
What are some alternatives?
liquibase - Main Liquibase Source
goose
dbmate - :rocket: A lightweight, framework-agnostic database migration tool.
goose - A database migration tool. Supports SQL migrations and Go functions.
migra - Like diff but for PostgreSQL schemas
pgx - PostgreSQL driver and toolkit for Go
jaeger-clickhouse - Jaeger ClickHouse storage plugin implementation
tern - The SQL Fan's Migrator
sqldef - Idempotent schema management for MySQL, PostgreSQL, and more
gormigrate - Minimalistic database migration helper for Gorm ORM
alembic - A database migrations tool for SQLAlchemy.
sqlx - general purpose extensions to golang's database/sql