They're visually distinct, and we shouldn't just alias one to the other just because it is not thoroughly tagged yet. An implication I guess is OK, but... there does need to be a way where images with both types present such as post #1851509 can be searched. Is there a particular tag we could use consistently for the former type of bag in those cases?
user #333214 Setsunator dmailed me about this, so bumping. From what I gathered I think he was trying to suggest school_briefcase and gym_bag as separate tags for the two kinds of bag, possibly implying school_bag, but I'll let him post here and clarify that himself.
In the interest of undoing the damage from the premature alias, perhaps albert or Toks could please do a bit of backend SQL magic to re-tag the posts that had school_briefcase removed by the aliasing process? The offending post changes are subset of version id 13280817 through 13281345, inclusive -- filter using updater id 23205 (me). Suggested SQL looks something like:
Show
Fix post_versions:
UPDATE post_versions
SET tags = // remove substring "-school_briefcase"
WHERE id>=13280817 AND id<=13281345 AND updater_id=23205
Fix post tags:
UPDATE posts
SET tag_string = // add "school_briefcase" tag if absent
WHERE id IN
SELECT post_id FROM post_versions
WHERE id>=13280817 AND id<=13281345 AND updater_id=23205
And whatever needs to be done to update tag indexing accordingly. This would, in effect, change the effect from aliasing to implication, which NWF Renim suggested above.
In the interest of undoing the damage from the premature alias, perhaps albert or Toks could please do a bit of backend SQL magic to re-tag the posts that had school_briefcase removed by the aliasing process? The offending post changes are subset of version id 13280817 through 13281345, inclusive -- filter using updater id 23205 (me). Suggested SQL looks something like:
Show
Fix post_versions:
UPDATE post_versions
SET tags = // remove substring "-school_briefcase"
WHERE id>=13280817 AND id<=13281345 AND updater_id=23205
Fix post tags:
UPDATE posts
SET tag_string = // add "school_briefcase" tag if absent
WHERE id IN
SELECT post_id FROM post_versions
WHERE id>=13280817 AND id<=13281345 AND updater_id=23205
And whatever needs to be done to update tag indexing accordingly. This would, in effect, change the effect from aliasing to implication, which NWF Renim suggested above.
I don't have sql query access to the database server, Albert is the only one who has that. Also running sql directly for this would result in the posts and tags becoming bugged out because you didn't run the callbacks in the rails code, so rails scripts are usually used.
Also the point of post versions is preserving the history of posts, so changing them months after the fact is never done.
Anyway, none of that matters since I just went to this page and ran a few lines of javascript to add the tag back to affected posts. It's much faster than writing a rails script and waiting for Albert to run it.
