I’d like to propose another attribute permissible on the column tag: defaultValueBinary.
It seems to me that each database has a different way of loading binary data into blobs, clobs and varbinary columns. However, the JDBC API unifies all these together with the setBlob() and setClob() APIs.
I would propose changing the XSD to permit such an attribute, standardize the text-representation of its value (perhaps hex notation, base64, something like that) and then changing the innards of Liquibase to detect such a value, if present, and use the relevant setBlob() calls to insert the value.
Obviously I’m just sketching here, but does this sound like a good idea? The end goal is to get the refactoring to deal with blob/binary data as well in a database-independent fashion.
Thanks,
Laird
-
Learn
-
Resources
-
Free Tools
OSS Risk Scanner Database DevOps Risk AssessmentCheat Sheets
Snowflake + Liquibase Databricks + Liquibase -
eBooks
6 Liquibase Community Risks & How to Avoid Guide: SOC 2 Compliance at the Database Layer Guide: Quantify the Value of Liquibase Secure -
Comparison Guides
Liquibase vs. Flyway Liquibase vs. Bytebase Liquibase Community vs Liquibase Secure
-
- Quickstart
- Get Started
- Documentation
- University
-
Resources
- Connect
- Contribute
- Join
- Blog