a8m

5 ms·

1.
Atlas v1.1: Database Security as Code and Declarative Data Management(atlasgo.io)
2 points by a8m 8mo ago|1 comments
2.
by a8m 8mo ago
We just shipped Atlas v1.1 - The focus of this release is Database Security as Code and Declarative Data Management. You can now declare database users, roles, permissions, and managed seed data as code - versioned, reviewed, and applied vi
3.
by a8m 8mo ago
Ariel from Atlas here. This setup is pretty common (declarative locally, versioned in real environments). Since migrations are auto-generated (by Atlas) on PRs, most developers never touch the versioned workflow directly. See: https:/
4.
by a8m 11mo ago
Good point regarding ORMs - that was one of the main problems I wanted to tackle when we built Atlas ( https://atlasgo.io ). We added support for reading ORM definitions directly, then let you extend the "base schema" de
5.
by a8m 2y ago
I'm glad to see I'm not the ~only one bothered by this issue. This has been, and still is, one of the challenges in managing MySQL schemas. That's one of the reasons we implemented "migrate down" differently than ot
6.
The Myth of Down Migrations(atlasgo.io)
6 points by a8m 3y ago|0 comments
7.
by a8m 3y ago
Check out: https://github.com/ariga/atlas . It’s like Terraform for databases. (I'm one of the authors of this project).
8.
by a8m 4y ago
Hey! For a long time, one of the most common feature requests we've been getting from our users is the ability to manage their desired "schema state" using SQL. For this reason, we're excited to announce the release of A
9.
by a8m 4y ago
Hey, I am the creator of entgo.io. I'm sorry to hear that your experience with the project was not great. I try to be available on our Discord, Slack, or the issue tracker, but sometimes I do miss some messages. If you ever consider to
10.
by a8m 4y ago
Just to emphasize, that OSS version of Ent models SQL tables in the traditional way (edges as foreign-keys and join-tables). i.e., the database structure is not obscure or something and can be easily read by developers and ported to other O
11.
by a8m 4y ago
Yes. The migration is built on top of Atlas: https://github.com/ariga/atlas
12.
by a8m 4y ago
Happy to share with you the new version of Atlas, the terraform for databases and a migration engine. There are many great features in this release, but one of the biggest features we added is multi-tenant support. Using this option, users
13.
by a8m 4y ago
Hey! Would love to share with you the latest release of Atlas - the migration engine we are working on. Currently, this tool provides a variety of capabilities for versioned migrations, including automatic migration authoring, linting migra
14.
Atlas Migration Execution Engine – Atlasgo.io(atlasgo.io)
3 points by a8m 4y ago|1 comments
15.
Prevent destructive changes to your database with the Atlas GitHub Action(atlasgo.io)
3 points by a8m 4y ago|0 comments
16.
Atlas, the “Terraform for databases” can now plan migrations for you(atlasgo.io)
1 points by a8m 4y ago|0 comments
17.
by a8m 5y ago
Views are going to be supported in the SQL-DDL version (see my comments below). I don't have any info about stored-procedures/triggers/events atm.
18.
by a8m 5y ago
I agree with that as well. The idea is to create an infrastructure for SQL parsers. Base parser will hold all standard structure and dialects can register custom clauses/statements. At the moment, I generate PEG files for each dialect,
19.
by a8m 5y ago
Thanks for the feedback. I'm one of the atlas's creator. At the moment, you can define schemas using Go (with a fluent API) or with HCL. The reason we decided to use HCL is because it can be easily extended, and our plans are to a
20.
by a8m 5y ago
Hey, I'm one of the atlas's creator. Thanks for the feedback. I'm actually familiar with all the things you mentioned here (I worked at FB too ;)), and some of them are the reasons why we decided to create atlas and OSS it. F
21.
by a8m 5y ago
Thanks for the blog-post Bodo! It's really pleasant to read.