Fix #2548436 (Use EVENT_TIMEZONE rather than TIMEZONE)

* Prior fix used the wrong column when adding time zone information
  to downloaded exceptions

Bug: 2548436
Change-Id: Idc1001fd58d2fba51823624a15862fe439c9ff6a
This commit is contained in:
Marc Blank 2010-03-26 12:13:01 -07:00
parent 41d17202f5
commit 4b4e00e4ce

View File

@ -535,7 +535,7 @@ public class CalendarSyncAdapter extends AbstractSyncAdapter {
cv.put(Events.ORIGINAL_ALL_DAY, parentCv.getAsInteger(Events.ALL_DAY));
cv.put(Events.EVENT_LOCATION, parentCv.getAsString(Events.EVENT_LOCATION));
cv.put(Events.VISIBILITY, parentCv.getAsString(Events.VISIBILITY));
cv.put(Events.TIMEZONE, parentCv.getAsString(Events.TIMEZONE));
cv.put(Events.EVENT_TIMEZONE, parentCv.getAsString(Events.EVENT_TIMEZONE));
// This column is the key that links the exception to the serverId
// TODO Make sure calendar knows this isn't globally unique!!