database-management

Environment

Liquibase Version: 4.3.5

Liquibase Integration & Version: CLI, Liquibase test-harness v1.0.1

Liquibase Extension(s) & Version: na

Database Vendor & Version: any

Operating System Type & Version: Windows 10

Description

Liqu

• Parser::parse: more complex examples, errors detecting
• Lexer::detokenize
• utils_sql (for splitQueries() check the CREATE TRIGGER)
• utils
• SelectResolver
• SchemaResolver

Why I need your help

Currently I'm working on a lot of features, which included adding support for different database types namely postgresql but that takes a lot of time and keeps me from adding the other features. So because of the time it takes I'm inclined to push back db support to the release after the upcoming one. But then still, it takes a lot of time.

My request

Is anyo

Describe the bug
Character greater then > breaks comment in formatter

To Reproduce
Steps to reproduce the behavior:

1. Go to https://vscode-sqltools.mteixeira.dev/playground/formatter
2. Click on insert into below text:
   -- comments are
   -- breaks by sign greater than >
   -- unfortunately
3. See error

Expected behavior
the comment should not be affected by a character grea

Currently, SchemaHero assumes that every Postgres table will be deployed to the public schema. It should be possible to specify the schema when defining a table

We don't want to build releases on any tags, just for releases