Issue Details (XML | Word | Printable)

Key: MBS-5255
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Normal Normal
Assignee: Aurélien Mino
Reporter: Aurélien Mino
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
MusicBrainz Server

Replication trigger for release_group_secondary_type_join is misnamed and duplicates trigger for release_group_secondary_type

Created: 02/Sep/12 08:51 AM   Updated: 04/Sep/12 01:52 PM   Resolved: 04/Sep/12 01:52 PM
Component/s: None
Affects Version/s: None
Fix Version/s: 2012-09-17


 Description  « Hide

CreateReplicationTriggers.sql

CREATE TRIGGER "reptg_release_group_secondary_type"
AFTER INSERT OR DELETE OR UPDATE ON "release_group_secondary_type"
FOR EACH ROW EXECUTE PROCEDURE "recordchange" ();

CREATE TRIGGER "reptg_release_group_secondary_type"
AFTER INSERT OR DELETE OR UPDATE ON "release_group_secondary_type_join"
FOR EACH ROW EXECUTE PROCEDURE "recordchange" ('verbose');

The fix is quite easy, but the big question is: what is running on production server? How this script hasn't failed on production server?



Sort Order: Ascending order - Click to sort in descending order
Aurélien Mino added a comment - 02/Sep/12 05:35 PM

the big question is: what is running on production server? How this script hasn't failed on production server?

According to Postgresql documentation, a trigger name has to be unique, but only for a given table.
So the current script doesn't generate an error. And is what has been run on production server.



Oliver Charles added a comment - 04/Sep/12 01:52 PM

These have been merged into the beta branch, but there's no beta testing to be done. This will all go live when we release.