xmlsitemap module
Update #6133
* Failed: DROP FUNCTION IF EXISTS first(anyelement, anyelement);
* DROP AGGREGATE first(anyelement)
* UPDATE {system} SET weight = 5 WHERE name = 'xmlsitemap'
* warning: pg_query() [function.pg-query]: Query failed: ERREUR: n'a pas pu supprimer fonction first(anyelement,anyelement) car d'autres objets en dépendent HINT: Utilisez DROP ... CASCADE pour supprimer aussi les objets dépendants. in /home/html/manifestation-contre-hadopi/includes/database.pgsql.inc on line 139.
* user warning: ERREUR: n'a pas pu supprimer fonction first(anyelement,anyelement) car d'autres objets en dépendent HINT: Utilisez DROP ... CASCADE pour supprimer aussi les objets dépendants. query: DROP FUNCTION IF EXISTS first(anyelement, anyelement); in /home/html/manifestation-contre-hadopi/sites/all/modules/xmlsitemap/xmlsitemap/xmlsitemap.install on line 662.
Comments
Comment #1
avpadernoThanks for the report. May you please translate the part of the error message written in French language?
My knowledgement of French language is limited; so far, I can only understand that it says it's not possible to drop the function
first(anyelement,anyelement)because of some dependences.Comment #2
grub3 commentedSorry. The message says : "Function cannot be dropped because it is used by other objects. You should use DROP CASCADE to drop dependant objects."
Comment #3
avpadernoThanks for the translation.
You can ignore the error message, as the module works the same; the update function is trying to remove an SQL function introduced and used by previous versions.
Comment #4
grub3 commentedIn fact, I could drop the function by hand. It seems that the object which used this function was dropped. So It is only a matter of ordering the drops : first the object, second the function. Should be easy to fix in code.
Comment #5
avpadernoMaybe it's enough to invert the first SQL queries that you reported;
DROP AGGREGATEshould maybe be executed first, and this would remove the dependent objects the error was speaking of.Comment #6
avpaderno@#4: This would confirm what I reported in #5.
I am lowering the level as the module works the same.
Comment #7
avpadernoThe code has been changed, and committed in CVS.
The code executes the queries in the right order; the message that would appear in case of error has been suppressed because the removal of the SQL function is completely optional, and the code continues to work even if that SQL function is present.
Thanks for your report.