From b4455aaf25a484b72d4df1795cb1f118b24d3434 Mon Sep 17 00:00:00 2001
From: Benjamin Neff <benjamin@coding4coffee.ch>
Date: Tue, 20 Sep 2016 10:13:34 +0200
Subject: [PATCH] Fix 20160906225138_fix_photos_share_visibilities.rb for
postgres
Turns out that postgres can't handle "0" as boolean, but mysql can
handle "false".
closes #7115#pullrequestreview-699342
---
db/migrate/20160906225138_fix_photos_share_visibilities.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/db/migrate/20160906225138_fix_photos_share_visibilities.rb b/db/migrate/20160906225138_fix_photos_share_visibilities.rb
index d14ca502cb..3621fe28b8 100644
--- a/db/migrate/20160906225138_fix_photos_share_visibilities.rb
+++ b/db/migrate/20160906225138_fix_photos_share_visibilities.rb
@@ -21,7 +21,7 @@ class FixPhotosShareVisibilities < ActiveRecord::Migration
"INNER JOIN posts ON posts.guid = photos.status_message_guid AND posts.type = 'StatusMessage' " \
"LEFT OUTER JOIN share_visibilities ON share_visibilities.shareable_id = photos.id " \
"INNER JOIN share_visibilities AS post_visibility ON post_visibility.shareable_id = posts.id " \
- "WHERE photos.public = 0 AND share_visibilities.shareable_id IS NULL " \
+ "WHERE photos.public = false AND share_visibilities.shareable_id IS NULL " \
"AND post_visibility.shareable_type = 'Post'"
end
--
GitLab