Troubleshooting of PostgreSQL: Difference between revisions

From LemonWiki共筆
Jump to navigation Jump to search
mNo edit summary
Tags: Mobile edit Mobile web edit
No edit summary
Line 16: Line 16:
</pre>
</pre>


References
* [https://www.geeksforgeeks.org/postgresql-limit-with-offset-clause/ PostgreSQL - LIMIT with OFFSET clause - GeeksforGeeks]
== ERROR:  argument of WHERE must be type boolean, not type integer ==
Query syntax mer error
<pre>
SELECT *
FROM my_table
WHERE 1
</pre>
Correct query syntax
<pre>
SELECT *
FROM my_table
WHERE 1 = 1
</pre>
or
<pre>
SELECT *
FROM my_table
WHERE TRUE
</pre>
References
* [https://stackoverflow.com/questions/242822/why-would-someone-use-where-1-1-and-conditions-in-a-sql-clause dynamic sql - Why would someone use WHERE 1=1 AND <conditions> in a SQL clause? - Stack Overflow]
== The numeric column data all became null after imported ==
[[Troubleshooting of Navicat for PostgreSQL]]


{{Template:Troubleshooting}}
{{Template:Troubleshooting}}

Revision as of 22:50, 11 October 2022

Troubleshooting of PostgreSQL

Syntax error: 7 ERROR: LIMIT #,# syntax is not supported

Query syntax mer error 

SELECT * 
FROM my_table
LIMIT 0,10

Correct query syntax 

SELECT * 
FROM my_table
LIMIT 10 OFFSET 0

References

ERROR: argument of WHERE must be type boolean, not type integer

Query syntax mer error 

SELECT * 
FROM my_table
WHERE 1

Correct query syntax 

SELECT * 
FROM my_table
WHERE 1 = 1

or 

SELECT * 
FROM my_table
WHERE TRUE

References

The numeric column data all became null after imported

Troubleshooting of Navicat for PostgreSQL


Troubleshooting of ...

Template

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