Troubleshooting of Navicat for PostgreSQL: Difference between revisions

From LemonWiki共筆
Jump to navigation Jump to search
(Created page with " == The numeric column data all became null after imported == * If the original data is Excel file, modify the format of the column from {{kbd | key=general}} to {{kbd | key=...")
 
No edit summary
 
(One intermediate revision by the same user not shown)
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}}


[[Category: PostgreSQL]]
[[Category:PostgreSQL]]
[[Category:Database]]
[[Category:Data Science]]
[[Category:Data Science]]

Latest revision as of 16:37, 18 April 2023

Troubleshooting of Navicat for PostgreSQL[edit]

How to fix The numeric column data all became null after imported[edit]

Solution:

  • If the original data is Excel file, modify the format of the column from general to numeric
  • import the data into Navicat for PostgreSQL again

How to fix ERROR: value too long for type character varying(255)[edit]

Solution:

  • Increase the length of the column from varchar(255) to text


Troubleshooting of ...

Template

Retrieved from "https://wiki.planetoid.info/index.php?title=Troubleshooting_of_Navicat_for_PostgreSQL&oldid=23637"