In this post, you take a look at how you can easily manage our database migration scripts by means of Liquibase.
#java #liquibase
1
1
0
0
Hashtag
#Liquibase
Advertisement · 728 × 90
New Liquibase research: AI & Production Databases interact in 96.5% of organizations, governance automation lags Liquibase, the leader in Database Change Governance, today released the 2026 St...
#Commentary #Liquibase
Origin | Interest | Match
0
0
0
0
Liquibase Secure 5.1 Extends Modeled Change Control to Snowflake Liquibase, the leader in Database Change Governance, today announced the release of Liquibase Secure 5.1, extending modeled Change C...
#Commentary #Liquibase
Origin | Interest | Match
0
0
0
0
0
0
0
0
In this post, you take a look at how you can easily manage our database migration scripts by means of Liquibase.
#java #liquibase
1
1
0
0
Liquibase Accelerates in FY25 as New ARR Rises More Than 85 Percent Liquibase today announced fiscal year 2025 momentum driven by accelerating new customer demand, record Liquibase Community adopti...
#Commentary #Liquibase
Origin | Interest | Match
0
0
0
0
#ITByte: #Liquibase is a powerful open-source tool in modern database development and DevOps practices.
By streamlining database schema changes Liquibase significantly enhances the efficiency and reliability of database deployments.
knowledgezone.co.in/posts/Liquib...
0
0
0
0
In this post, you take a look at how you can easily manage our database migration scripts by means of Liquibase.
#java #liquibase
1
1
0
0
Liquibase Secure Extends AI Governance to the Database Layer, Closing the Gap Between AI Safety and Data Integrity Liquibase today announced new AI governance capabilities in Liquibase Secure, exte...
#Commentary #Liquibase
Origin | Interest | Match
0
0
0
0
I recently read and shared You’re Wasting Time in #Java Without These 10 Libraries. I commented on it a bit in my newsletter, but given the amount and intensity of reactions, I think a full-blown post is in order.
#Lombok #JUnit #Jackson #SpringFramework #Liquibase #Flyway #SLF4J #Log4J2
7
4
0
0
In this post, you take a look at how you can easily manage our database migration scripts by means of Liquibase.
#java #liquibase
2
1
0
0
The are a bunch of #FOSS projects which are using #Liquibase and which cannot move to Liquibase 5.x or later due to its license change.
github.com/keycloak/key...
github.com/liquibase/li...
Dependent projects on Maven Central:
central.sonatype.com/artifact/org...
#Java #OSS #licensing
1
1
0
0
🤔 Just wondering: if somebody forked the last version of #Liquibase which was published under Apache License, Version 2.0, would there actually be interest in a) using this fork and, more important, b) contributing to this fork?
#Java #OSS #licensing
1
2
2
0
🤔 Just wondering: if somebody forked the last version of #Liquibase which was published under Apache License, Version 2.0, would there actually be interest in a) using this fork and more important b) contributing to this fork?
https://hachyderm.io/@joschi/115323556944325877
The are a bunch of […]
1
1
0
0
I'm surprised that there wasn't more noise around the license change of #Liquibase from Apache License 2.0 to Functional Source License (FSL) in Liquibase 5.0.0.
github.com/liquibase/liquibase/rele...
Is just nobody using it anymore? 😅
#Java #OSS #licensing
3
4
2
0
I'm surprised that there wasn't more noise around the license change of #Liquibase from Apache License 2.0 to Functional Source License (FSL) in Liquibase 5.0.0.
github.com/liquibase/li...
Is just nobody using it anymore? 😅
#Java #OSS #licensing
13
11
4
2
## Me I just wonder if this is a situation where MARK_RAN is wiser than CONTINUE. ## AI Assistant **Great question!** You're thinking about the right nuance here. Let's compare for this specific scenario: ## **CONTINUE** (current choice) - Skips the changeset SQL when preconditions fail - **Still marks the changeset as executed** in DATABASECHANGELOG - On subsequent runs: Won't check preconditions again, won't run SQL again ## **MARK_RAN** - Skips the changeset SQL when preconditions fail - **Marks it as executed in DATABASECHANGELOG** - Explicitly indicates "this was intentionally skipped due to preconditions" - Same end result, but semantically clearer intent ## **For your use case, I'd argue MARK_RAN is slightly better:** **Why?** 1. **Semantic clarity** - You're checking state before running a migration. If the Daily export already exists, you _intentionally_ don't want to run the UPDATE. That's exactly what `MARK_RAN` communicates. 2. **Audit trail** - Someone reviewing the changelog execution history will see that preconditions were evaluated and the changeset was deliberately skipped (not that it continued past an error/warning). 3. **The practical difference is minimal** - Both work correctly here. But `MARK_RAN` better expresses "I checked, the work is already done, moving on" vs. `CONTINUE` which feels more like "something wasn't right, but keep going."
The following "AI Assistant" interaction is with Claude 4.5 Sonnet.
This #AI is super confident in describing how #Liquibase behaves with onFail="CONTINUE" in the preConditions.
It's also flatly wrong, in a way that could be disastrous in production code.
Has the AI assistant helped me catch...
1
0
1
0
In this post, you take a look at how you can easily manage our database migration scripts by means of Liquibase.
#java #liquibase
4
2
0
0
👾New CyberJAR Episode: Liquibase Step-By-Step
An ultimate guide to using #Liquibase with #SpringBoot and Maven: YAML/SQL scripts, preConditions, rollbacks, diffs, and running migrations in CI/CD:
www.youtube.com/watch?v=a1vG...
2
2
1
0
In this post, you take a look at how you can easily manage our database migration scripts by means of Liquibase.
#java #liquibase
1
1
0
0
In this post, you take a look at how you can easily manage our database migration scripts by means of Liquibase.
#java #liquibase
2
1
0
0
In this post, you take a look at how you can easily manage our database migration scripts by means of Liquibase.
#java #liquibase
3
1
0
0
Liquibase Preconditions Example Liquibase is a popular open-source database schema change managem...
www.javacodegeeks.com/liquibase-preconditions-...
#Software #Development #Liquibase
Event Attributes
0
0
0
0
I’ve used #Liquibase for a long time, but #SQLcl Projects caught my attention. After days (and nights) of exploring, I’m hooked! So much so that @arvidregenberg.bsky.social and I started blogging.
We compare Liquibase & SQLcl Projects (incl. #orclAPEX). Check it out & share your thoughts! 🚀
9
4
0
0
Database Migrations in the Real World Database migrations are critical to modern application deve...
blog.jetbrains.com/idea/2025/02/database-mi...
#idea #database #flyway #intellij-idea #liquibase #migrations
Event Attributes
0
0
0
0
Database Migrations in the Real World Database migrations are critical to modern application deve...
blog.jetbrains.com/idea/2025/02/database-mi...
#idea #database #flyway #intellij-idea #liquibase #migrations
Event Attributes
0
0
0
0
Database Migrations in the Real World Database migrations are critical to modern application deve...
blog.jetbrains.com/idea/2025/02/database-mi...
#idea #database #flyway #intellij-idea #liquibase #migrations
Event Attributes
0
0
0
0
#ITByte: #Liquibase is a powerful open-source tool in modern database development and DevOps practices.
By streamlining database schema changes, Liquibase significantly enhances the efficiency and reliability of database deployments.
knowledgezone.co.in/posts/Liquib...
0
0
0
0
IMO terrible practice to introduce this as opt-out. Especially in a minor release.
Our firewall has our back, but if this is #liquibase ethics to push FOSS users into a paid plan then I'll gladly reconsider using the tool at all.
4
3
1
0
It is always worthwhile to read changelogs.
For example, #liquibase 4.30.0 and above will now collect statistics (#telemetry) with opt-out instead of opt-in. Thanks for nothing.
New #java projects will be using #flyway.
docs.liquibase.com/analytics/ho...
8
5
4
4