[Calendar and Contacts Server] #405: getetag return None in calendar folders when using sql datastore backend
#405: getetag return None in calendar folders when using sql datastore backend ------------------------------+--------------------------------------------- Reporter: pedro@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: | Radar: ------------------------------+--------------------------------------------- getetags must return a consistent value that helps keeping track of folder changes. I have traced the bug to the file md5() function in CommonHomeChild class within txdav/common/datastore/sql.py. This function return None always. -- Ticket URL: <http://trac.calendarserver.org/ticket/405> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server
#405: getetag return None in calendar folders when using sql datastore backend ------------------------------+--------------------------------------------- Reporter: pedro@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: | Radar: ------------------------------+--------------------------------------------- Comment(by mail@…): Just to clarify: In source:/CalendarServer/trunk/txdav/common/datastore/sql.py@6909#L1663 there is in fact simply none returned. {{{ def md5(self): return None }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/405#comment:1> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server
#405: getetag return None in calendar folders when using sql datastore backend --------------------------------+------------------------------------------- Reporter: pedro@… | Owner: wsanchez@… Type: Defect | Status: closed Priority: 5: Not set | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Resolution: Behaves correctly | Keywords: Radar: | --------------------------------+------------------------------------------- Changes (by wsanchez@…): * status: new => closed * resolution: => Behaves correctly Comment: ETags are not an appropriate way to track changes to collection resources; it's only a good way to track the *rendered representation* of a collection. There is no requirement that ETags change when collections add or remove members, etc. This is why we invented CTags as a work-around and now support the sync report. -- Ticket URL: <http://trac.calendarserver.org/ticket/405#comment:2> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server
participants (1)
-
Calendar and Contacts Server