Troubleshooting of Navicat for PostgreSQL: Difference between revisions
Jump to navigation
Jump to search
Troubleshooting of Navicat for PostgreSQL (edit)
Revision as of 16:37, 18 April 2023
, 18 April 2023no edit summary
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== The numeric column data all became null after imported == | == Troubleshooting of Navicat for PostgreSQL == | ||
=== How to fix The numeric column data all became null after imported === | |||
Solution: | |||
* If the original data is Excel file, modify the format of the column from {{kbd | key=general}} to {{kbd | key=numeric}} | * If the original data is Excel file, modify the format of the column from {{kbd | key=general}} to {{kbd | key=numeric}} | ||
* import the data into Navicat for PostgreSQL again | * import the data into Navicat for PostgreSQL again | ||
=== How to fix ERROR: value too long for type character varying(255) === | |||
Solution: | |||
* Increase the length of the column from varchar(255) to text | |||
{{Template:Troubleshooting}} | {{Template:Troubleshooting}} | ||