Skip to content

Commit 5fff111

Browse files
committed
docs: explain that rollbacks are not supported
1 parent 632a7fe commit 5fff111

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,6 @@
1212
</p>
1313
</div>
1414

15-
## Motivation
16-
1715
Laravel's schema builder and migration system are great for managing tables and
1816
indexes---but offer no built-in support for other SQL entities, such as
1917
(materialized) views, procedures, functions, and triggers.
@@ -33,6 +31,11 @@ Whether you're managing reporting views, business logic functions, or automation
3331
triggers, this package helps you treat SQL entities like real, versioned parts
3432
of your codebase---no more scattered SQL in migrations!
3533

34+
> [!NOTE]
35+
> Migration rollbacks are not supported since the definitions always reflect the latest state.
36+
>
37+
> ["We're never going backwards. You only go forward." -Taylor Otwell](https://www.twitch.tv/theprimeagen/clip/DrabAltruisticEggnogVoHiYo-f6CVkrqraPsWrEht)
38+
3639
## Installation
3740

3841
First pull in the package using Composer:

0 commit comments

Comments
 (0)