[CalendarServer-changes] [8534] CalendarServer/branches/users/glyph/skip-lonely-vtimezones
source_changes at macosforge.org
source_changes at macosforge.org
Fri Jan 13 14:03:23 PST 2012
Revision: 8534
http://trac.macosforge.org/projects/calendarserver/changeset/8534
Author: glyph at apple.com
Date: 2012-01-13 14:03:23 -0800 (Fri, 13 Jan 2012)
Log Message:
-----------
better test docstring
Modified Paths:
--------------
CalendarServer/branches/users/glyph/skip-lonely-vtimezones/txdav/common/datastore/upgrade/test/test_migrate.py
Property Changed:
----------------
CalendarServer/branches/users/glyph/skip-lonely-vtimezones/
Modified: CalendarServer/branches/users/glyph/skip-lonely-vtimezones/txdav/common/datastore/upgrade/test/test_migrate.py
===================================================================
--- CalendarServer/branches/users/glyph/skip-lonely-vtimezones/txdav/common/datastore/upgrade/test/test_migrate.py 2012-01-13 22:03:20 UTC (rev 8533)
+++ CalendarServer/branches/users/glyph/skip-lonely-vtimezones/txdav/common/datastore/upgrade/test/test_migrate.py 2012-01-13 22:03:23 UTC (rev 8534)
@@ -197,10 +197,12 @@
}
)
@inlineCallbacks
- def test_justVEvent(self):
+ def test_unknownTypeNotMigrated(self):
"""
- Calendar objects that are free-standing VTIMEZONEs are dropped and not
- migrated from the filesystem to the database.
+ The only types of calendar objects that should get migrated are VEVENTs
+ and VTODOs. Other component types, such as free-standing VTIMEZONEs,
+ don't have a UID and can't be stored properly in the database, so they
+ should not be migrated.
"""
self.topService.startService()
txn = self.sqlStore.newTransaction()
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/calendarserver-changes/attachments/20120113/f0ea18c3/attachment.html>
More information about the calendarserver-changes
mailing list