I'm using GUI (right click -> drop) but I also tried to copy DROP FUNCTION to the query window, same result.
Syntax error when trying to drop function in postgresql (pgsql)
Yes, the function editor has much MySQL stuff in it. But information_schema.routines should exist on PostgreSQL too, or?
The "DROP FUNCTION xyz" is MySQL and PostgreSQL syntax, according to the documentation. Which server version is it on your side? Probably we need a version conditional here.
The "DROP FUNCTION xyz" is MySQL and PostgreSQL syntax, according to the documentation. Which server version is it on your side? Probably we need a version conditional here.
Precisely, it does support it. Alrighty. I clearly understand that pgsql is experimental and not your priority. You developed a wonderful software.
Also for some reason function editor says that "CREATE code" that
CREATE FUNCTION "check1a"("student_id" UNKNOWN)
where it should be
CREATE FUNCTION "check1a"("student_id" VARCHAR(5))
so it incorrectly recognizes the data type, without it, you won't be able to drop function properly. Same happens (also shows UNKNOWN) in "Parameters" tab
Also for some reason function editor says that "CREATE code" that
CREATE FUNCTION "check1a"("student_id" UNKNOWN)
where it should be
CREATE FUNCTION "check1a"("student_id" VARCHAR(5))
so it incorrectly recognizes the data type, without it, you won't be able to drop function properly. Same happens (also shows UNKNOWN) in "Parameters" tab
Code modification/commit
from ansgarbecker,
9 years ago,
revision 9.1.0.4943
Support dropping functions and procedures on PostgreSQL, which requires the parameters list in parentheses. See http://www.heidisql.com/forum.php?t=18198
r4943 now adds the parameters list to the DROP FUNCTION query.
This also solves another problem:
* Very first and very last parameters in PG function were never detected. This most probably includes your VARCHAR(5) parameter.
Unfortunately, this does not yet solve another problem:
* HeidiSQL always uses the first physically available function, when having two or more functions with the same name but different parameters
This also solves another problem:
* Very first and very last parameters in PG function were never detected. This most probably includes your VARCHAR(5) parameter.
Unfortunately, this does not yet solve another problem:
* HeidiSQL always uses the first physically available function, when having two or more functions with the same name but different parameters
Please login to leave a reply, or register at first.