Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitdb91558

Browse files
Bump version to flyway-11.17.1
Please see the GH release for the release notesadd support for configuring different root namespaces via the command-lineCloses#4169: Fixes an additional connection being created when running migrate
1 parent6ac640f commitdb91558

File tree

228 files changed

+1718
-665
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

228 files changed

+1718
-665
lines changed

‎documentation/Reference/Code Analysis Rules/Configuring SQLFluff Rules.md‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -85,3 +85,22 @@ This is the most granular change and just [ignores violation on an individual li
8585
-- Ignore rule CP02 & rule CP03
8686
SeLeCt1from tBl ;-- noqa: CP02,CP03
8787
```
88+
89+
##Reporting`--noqa` Tag Usage
90+
{% include enterprise.html %}
91+
92+
Using`--noqa` tags to suppress SQLFluff code analysis rules introduces risks, as those statements will bypass linting checks.
93+
94+
To help mitigate this, Flyway generates a warning-level violation whenever a`--noqa` tag is detected.
95+
96+
In the command-line output, you will see something similar to the following:
97+
98+
```
99+
+--------------------+-----------+------------------+----------+
100+
| Engine | Rule Code | Violations Count | Severity |
101+
+--------------------+-----------+------------------+----------+
102+
| SQLFluff (Redgate) | RG01 | 1 | Error |
103+
| SQLFluff (Redgate) | RG02 | 1 | Error |
104+
| Policy Overrides | noqa | 4 | Warning |
105+
+--------------------+-----------+------------------+----------+
106+
```

‎documentation/Reference/Code Analysis Rules/Redgate SQLFluff Rules Library.md‎

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ subtitle: Redgate SQLFluff Rules Library
66
##Accessing Redgate SQLFluff Rules
77
Flyway CLI ships with a packaged version of SQLFluff that includes additional rules written by Redgate.
88

9-
If you are using thepackaged version of SQLFluff then you will see something like this in the CLI output
9+
If you are using theRedgate bundled version of SQLFluff then you will see something like this in the CLI output
1010
```
11-
SqlFluff version 3.4.2 (Packaged)
11+
SqlFluff version 3.4.2 (Redgate Bundle)
1212
```
1313
These rules are under development so expect the list to grow.
1414

@@ -158,3 +158,11 @@ A CREATE ROLE statement may require review to ensure proper access restrictions.
158158
Altering privileges for PUBLIC is discouraged, consider using explicit roles.
159159
###Groups:`all`,`redgate`
160160
###Dialects supported:`all`
161+
162+
---
163+
{% include anchor.html link="RG13"%}
164+
#Rule: RG13 TRUNCATE Statement
165+
##Check for TRUNCATE statements
166+
TRUNCATE statements will remove all rows of data in the table
167+
###Groups:`all`,`redgate`
168+
###Dialects supported:`all`

‎documentation/Reference/Commands/Snapshot.md‎

Lines changed: 17 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,8 @@ Be sure to set [environment schemas](<Configuration/Environments Namespace/Envir
1515
a snapshot for Oracle databases.
1616

1717
Snapshots may be stored in the snapshot history table by specifying an appropriate location using the
18-
[`filename`](<Configuration/Flyway Namespace/Flyway Snapshot Namespace/Flyway Snapshot Source Setting>) parameter. In this case, Flyway will create the snapshot history table automatically if it doesn't exist.
18+
[`filename`](<Configuration/Flyway Namespace/Flyway Snapshot Namespace/Flyway Snapshot Source Setting>) parameter. In
19+
this case, Flyway will create the snapshot history table automatically if it doesn't exist.
1920

2021
See[Snapshots](https://documentation.red-gate.com/display/FD/Snapshots) for more information.
2122

@@ -105,4 +106,18 @@ the [Flyway namespace](<Configuration/Flyway Namespace>) can also be set:
105106
This command can produce the following error codes:
106107

107108
-[Generic error codes](<Exit codes and error codes/General error codes>)
108-
-[Comparison error codes](<Exit codes and error codes/Comparison error codes>)
109+
-[Comparison error codes](<Exit codes and error codes/Comparison error codes>)
110+
111+
###Database Binary size limits
112+
113+
When storing snapshots to
114+
the[Flyway Snapshot History Table](<Configuration/Flyway Namespace/flyway-snapshot-namespace/flyway-snapshot-history-table-setting>),
115+
there is a size constraint.
116+
The snapshots will be compressed before insertion into the table, so the constraint only applies after compression.
117+
118+
| Database| Datatype| Size|
119+
|------------|----------------|------|
120+
| SQL Server| VARBINARY(MAX)| 2Gb|
121+
| Oracle| BLOB| 4Gb|
122+
| MySQL| LONGBLOB| 2Gb|
123+
| PostgreSQL| BYTEA| 1Gb|
Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
subtitle:testConnection
3+
---
4+
5+
##Description
6+
The`testConnection` command attempts to establish a connection to the database using the configured[environment](<Configuration/Flyway Namespace/Flyway Environment Setting>).
7+
This command is designed to verify that Flyway and other engines used by Flyway can reach your database, ensuring the connectivity and configuration are correct before running migrations or other operations.
8+
9+
Currently supported engines:
10+
- Flyway Engine
11+
- Comparison Engines
12+
13+
If no environment is specified, the default environment will be used, if it exists.
14+
15+
- On success: Displays 'Connection successful' for each successful engine connected and exits with a status code 0.
16+
- On failure: Displays database specific connection error with diagnostic information and a non-zero status code.
17+
- On success with JSON output: Displays a message that lists the engines that Flyway connected to
18+
19+
This command only returns output and does not make any changes to your database; unlike[info](<Commands/Info>) which may also trigger callbacks, migration validation or checksum evaluation.
20+
21+
###Usage Example
22+
23+
####Test connection to the development environment via command line
24+
```sh
25+
flyway testConnection -environment=development
26+
```
27+
28+
29+
##Parameters
30+
31+
- All standard Flyway configuration options that affect connection (e.g.,`-url`,`-user`,`-password`, or environment selection like`-environment={name}`) are supported.
32+
33+
34+
_For a full list of configuration options, see[Flyway configuration](https://documentation.red-gate.com/flyway/reference/configuration/)._
35+
36+
37+
##JSON output format
38+
39+
```json
40+
{
41+
"successfulConnections" :"Flyway"
42+
}
43+
```

‎documentation/Reference/Configuration/Flyway Namespace/Flyway Check Namespace/Flyway Check Rules Config Setting.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ String
1818

1919
##Default
2020

21-
Flyway’spackaged version of SQLFluff will look for`sqlfluff.cfg` in the`conf/` folder of the Flyway installation.
21+
Flyway’sRedgate Bundle version of SQLFluff will look for`sqlfluff.cfg` in the`conf/` folder of the Flyway installation.
2222

2323
If you're using your own installed version of SQLFluff, Flyway will not attempt to load any default configuration file.
2424

‎documentation/Reference/Configuration/Flyway Namespace/Flyway Check Namespace/Flyway Check SQLFluff Enabled Setting.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ sqlfluffEnabled = false
3737
flyway.check.sqlfluffEnabled=false
3838
```
3939

40-
###Packaged`SQLFluff` Engine
40+
###Redgate Bundle`SQLFluff` Engine
4141

4242
{% include enterprise.html %}
4343

‎documentation/Reference/Configuration/Flyway Namespace/Flyway Check Namespace/Flyway Check Scope Setting.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,13 @@ subtitle: flyway.check.scope
66

77
##Description
88

9-
If this parameter is specified, Flyway will use it to determine the scope ofmigrationfiles to include in code analysis.
9+
If this parameter is specified, Flyway will use it to determine the scope of files to include in code analysis.
1010

1111
__Note:__ Only the following values are valid for this parameter (case-insensitive):
1212
- DEFAULT
1313
- ALL
1414
- PENDING
15+
- SCRIPT
1516

1617
##Type
1718

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
subtitle:flyway.check.scriptFilename
3+
---
4+
5+
{% include commandlineonly.html %}
6+
7+
##Description
8+
9+
Specify an individual script to run code analysis on. Only used if[scope](<Configuration/Flyway Namespace/Flyway Check Namespace/Flyway Check Scope Setting>) is 'SCRIPT'.
10+
This will be resolved relative to the[working directory](<Command-line Parameters/Working Directory Parameter>).
11+
12+
##Type
13+
14+
String
15+
16+
##Default
17+
18+
`deployments/D__deployment.sql`
19+
20+
##Usage
21+
22+
###Command-line
23+
24+
```powershell
25+
./flyway check -code -check.scriptFilename=custom_script.sql
26+
```
27+
28+
###TOML Configuration File
29+
30+
```toml
31+
[flyway.check]
32+
scriptFilename ="custom_script.sql"
33+
```

‎documentation/Reference/Configuration/Flyway Namespace/Flyway DIff Namespace/Flyway Diff Source Setting.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@ String
1717
-`"schemaModel"` - the schema model folder referenced by[`schemaModelLocation`](<Configuration/Flyway Namespace/Flyway Schema Model Location Setting>)
1818
-`"migrations"` - uses a buildEnvironment to represent the state of database after specified migrations have been applied
1919
-`"snapshot:<<path>>"` - uses a snapshot file at the specified path
20+
-`"snapshotHistory:<<name>>"` - uses a snapshot entry in the[snapshot history table](<Configuration/Flyway Namespace/Flyway Snapshot Namespace/Flyway Snapshot History Table Setting>); entries are either identified by name, or`current` for the most recent snapshot, or`previous` for the most recent but one.
2021

2122
In the case where an environment shares a name with one of the other values, it can be prefixed with`env:`
2223

‎documentation/Reference/Configuration/Flyway Namespace/Flyway DIff Namespace/Flyway Diff Target Setting.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@ String
1717
-`"schemaModel"` - the schema model folder referenced by[`schemaModelLocation`](<Configuration/Flyway Namespace/Flyway Schema Model Location Setting>)
1818
-`"migrations"` - uses a buildEnvironment to represent the state of database after specified migrations have been applied
1919
-`"snapshot:<<path>>"` - uses a snapshot file at the specified path
20+
-`"snapshotHistory:<<name>>"` - uses a snapshot entry in the[snapshot history table](<Configuration/Flyway Namespace/Flyway Snapshot Namespace/Flyway Snapshot History Table Setting>); entries are either identified by name, or`current` for the most recent snapshot, or`previous` for the most recent but one.
2021

2122
In the case where an environment shares a name with one of the other values, it can be prefixed with`env:`
2223

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp