15,063
edits
Troubleshooting of PostgreSQL: Difference between revisions
Jump to navigation
Jump to search
m
→How to fix Syntax error of PostgreSQL
| Line 1: | Line 1: | ||
Troubleshooting of [https://www.postgresql.org/ PostgreSQL] | Troubleshooting of [https://www.postgresql.org/ PostgreSQL] | ||
== | == Troubleshooting of PostgreSQL == | ||
=== How to fix Syntax error: 7 ERROR: LIMIT #,# syntax is not supported === | === How to fix Syntax error: 7 ERROR: LIMIT #,# syntax is not supported === | ||
Query syntax mer error | Query syntax mer error | ||
| Line 87: | Line 87: | ||
=== How to fix: The numeric column data all became null after imported === | === How to fix: The numeric column data all became null after imported === | ||
[[Troubleshooting of Navicat for PostgreSQL]] | [[Troubleshooting of Navicat for PostgreSQL]] | ||
=== pgAdmin 4 on macOS Has No Autocomplete for Field or Table Names === | |||
pgAdmin 4 has autocomplete built in by default, but it sometimes needs to be triggered manually or configured first. | |||
'''How to trigger it''' | |||
In the Query Tool, press `Ctrl / Cmd + Space`. However, on macOS, `Ctrl + Space` is reserved for switching input methods, and `Cmd + Space` opens Spotlight — so the shortcut conflict likely prevents the autocomplete menu from appearing. This menu is what normally shows suggestions for tables, columns, schemas, and keywords. | |||
'''How to make autocomplete appear as you type''' | |||
# Windows / Linux: Go to File → Preferences → Query Tool → Auto Completion, and make sure "Keywords autocomplete?" is checked. | |||
# Mac: Go to pgAdmin 4 → Preferences → Query Tool → Auto Completion, and make sure "Keywords autocomplete?" is checked. | |||
== Further reading == | == Further reading == | ||