Mapless VS bytebase

Just a quick update to mention that I've merged in develop a pull request that will add the capability to work with Mapless using UnQLite in memory.

Sounds like it was a smooth migration. Good to hear that because in this precise moment I'm adding SQLite support to *Mapless* [1] (PostgreSQL had support already [2]) so people can do these kind of smooth transitions in their Smalltalk apps.

[1] https://github.com/sebastianconcept/Mapless

[2] https://blog.sebastiansastre.co/article/mapless-is-online-ag...

After quite some time not having updates on Mapless, I've invested in getting it working for latests Pharo versions and incorporating and maturing its API and main features.

1. Circa 2014 I've created Mapless [1], a Smalltalk persistence framework to remove the Object Relational Impedance Mismatch problem by design so I can quickly prototype or (modify) maintain the persisted objects without caring about mapping. Now it's going for production with humongous load.

2. I'm discretely working in Lobster [2] because I don't like current Smalltalk IDEs and I want one with a native look and feel. So far I have implemented Transcript, Workspace, Inspector, REPL and partially a Class Hierarchy Browser.

[1] https://github.com/sebastianconcept/Mapless

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...

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.

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.

bytebase.com — Database CI/CD and DevOps. Free under 20 users and ten database instances

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.

Now there are more subdivided practice: * Policy as Code: Sentinel, OPA * Database as Code: bytebase * AppConfiguration as Code: KusionStack, Acorn * ...... (Welcome to add more)

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.

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.