Categorize LIMIT ALL as PostgreSQL-specific

nene · Jan 17, 2024 · f762442 · f762442
1 parent 9260b58
commit f762442
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/STYLE_GUIDE.md b/STYLE_GUIDE.md
@@ -149,7 +149,6 @@ Some candidates:
 - `DROP` -> `DROP COLUMN` (more commonly supported)
 - `ALTER` -> `ALTER COLUMN` (more commonly supported)
 - :white_check_mark: :wrench: `RENAME new_table_name` -> `RENAME TO new_table_name` (more commonly supported)
-- `LIMIT ALL` -> (it's the same as specifying no limit)
 
 A related case is the use of non-standard function names where standard alternatives are available, like:
 
@@ -175,6 +174,7 @@ So the pretty-printer probably shouldn't eliminate such redundant syntax.
 ### PostgreSQL
 
 - :white_check_mark: :wrench: Convert deprecated `:=` named argument syntax to standard `=>`.
+- :question: `LIMIT ALL` -> (it's the same as specifying no limit)
 
 ### MySQL