Open issues

Allow SqlScriptMigration to optionally split statements
MVWB-183
Simplify PicoCLI integration
MVWB-181
Make it easier to compose plugins for WildebeestApi
MVWB-180
XSD resources not being included in the core JAR
MVWB-178
Refactor assertionrefs to resolve at runtime rather than deserialize time
MVWB-177
Make unit tests log to stdout
MVWB-175
Create DomInstanceLoader unit test suite
MVWB-170
Blog Post: Streaming Wildebeest events to AWS CloudWatch
MVWB-169
Blog Post: Streaming WIldebeest events to Elastic Stack
MVWB-168
Installer with Bundled JRE
MVWB-167
Unit test code coverage report
MVWB-164
SLF4J config to log to file
MVWB-162
Get PrintStream out of WildebeestApiImpl and lower tiers
MVWB-159
Add demo recorded with asciicinema
MVWB-157
Selector Assertion Refs
MVWB-155
jumpstate could be misused
MVWB-153
DomBuilder.reset() - remove?
MVWB-150
Blog: DataOps
MVWB-144
Move Wildebeest website to mv.com
MVWB-143
SQL Server Table Assertions dont output schemaName
MVWB-142
Release Wildebeest 4.0
MVWB-140
Exception when using JumpState to bring existing SQL Server resources under WIldebeest management
MVWB-139
Research Bering for database upgrade / downgrade management
MVWB-137
Javadocs
MVWB-136
Email list for Wildebeest project updates
MVWB-135
Blog section on website to publish releases, news, tutorials, etc
MVWB-134
Running "state" on an existing unmanaged SQL Server database throws
MVWB-128
Samples and auto-generate output for website
MVWB-125
Resource references
MVWB-124
Improve validation for unknown targets
MVWB-123
Windows Desktop App
MVWB-122
Wildebeest Blog
MVWB-121
Drop unnecessary surrogate keys
MVWB-120
Assertion Applicability
MVWB-118
Option to run database migrates in a transaction
MVWB-117
Mutable Instance objects
MVWB-116
migrate-to-at-least
MVWB-115
Unit and Integration Test Suite
MVWB-109
Composite Resources
MVWB-108
SQL Server Resource Support
MVWB-103
PostgreSql Resource Support
MVWB-102
A set of plugins that can be used to define a resource which can target different RDBMS platforms.
MVWB-100
Log migration to structured XML file
MVWB-96
DropTableMigration
MVWB-95
Revise Introduction
MVWB-93
Document In-App Embedding
MVWB-84
Manual Migration Steps
MVWB-83
Release Archive
MVWB-81
DOM Builder Unit Tests
MVWB-78
Windows Desktop Log Viewer App
MVWB-75
issue 1 of 73

Allow SqlScriptMigration to optionally split statements

Description

Currently by default the SqlScriptMigration always splits SQL statements at semicolon. As I recall I added this because I encountered issues with runnng batches of statements on MySQL. In some cases this causes problems though - currently encountering it with PostgreSQL when trying to run a CREATE FUNCTION that contains a couple of semi-colons in the body of the function. These cause the function to be split incorrectly which fails.

As an interim solution we will add a settable flag on SqlScriptMigration that allows you to specify if statements should be split or not.

Status

Assignee

Unassigned

Reporter

Brendon Matheson

Labels

None

Sprint

Priority

Medium
Configure