begin
# The "prefs" table uses the normal username as a key...
# This should be harmless if the source user does not exist.
- sql_query = 'UPDATE prefs SET username = $1 WHERE username = $2;'
- connection.query(sql_query, [dst.to_s(), src.to_s()])
+ sql_query0 = 'UPDATE prefs SET username = $1 WHERE username = $2;'
+ connection.query(sql_query0, [dst.to_s(), src.to_s()])
# But the "shares" table uses encoded principal URLs. For the
# "shares" table, we need to do a find/replace on the username
# calendar URL will change when a user moves. This will ALSO
# affect people who name their calendars something like
# "user%40example.com", but screw those people.
- sql_queries << 'UPDATE shares SET owner=REPLACE(owner, $2, $1);'
+ sql_queries = ['UPDATE shares SET owner=REPLACE(owner, $2, $1);']
sql_queries << 'UPDATE shares SET calendar=REPLACE(calendar, $2, $1);'
- sql_queries << 'UPDATE shares SET with=REPLACE(with, $2, $1);'
+ sql_queries << 'UPDATE shares SET "with"=REPLACE("with", $2, $1);'
sql_queries.each do |sql_query|
connection.query(sql_query, [encoded_dst, encoded_src])
# of the user's email address in the "calendar" field happens when
# he is also the owner, so the calendar does get deleted in the
# normal situation.
- sql_queries << "DELETE FROM shares WHERE REPLACE(owner, '%40', '@') ~ $1;"
- sql_queries << "DELETE FROM shares WHERE REPLACE(with, '%40', '@') ~ $1;"
+ sql_queries << "DELETE FROM shares WHERE REPLACE(owner,'%40','@') ~ $1;"
+ sql_queries << "DELETE FROM shares WHERE REPLACE(\"with\",'%40','@') ~ $1;"
connection = PG::Connection.new(@db_hash)
begin