[Tickets #12617] Re: Most drivers don't implement 'fetch_tags' feature

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12617
------------------------------------------------------------------------------
  Ticket             | 12617
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Most drivers don't implement 'fetch_tags' feature
  Queue              | Kronolith
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2013-09-03 14:38) wrote:

>> Well, only the drivers that actually use tags need this.
> This is probably not quite correct, theoretically any driver could  
> implement tagging, because the tags are stored independent from the  
> calendar storage. At least all backends with read-write support  
> should support tagging

These would  still be "only the drivers that use tags". The parameter  
is available to any driver that wants to make use of it. It's just  
that currently, only the SQL driver (and maybe Kolab - don't have code  
handy to look) actually fall under this category.

I would say that non-horde backends should only support tagging if the  
storage backend for the event itself understands them (be they called  
"tags" or "categories" or whatever). Otherwise, the user will be  
"surprised" when tags that were entered in Horde do not appear in the  
event data when accessed via another client. Otherwise, yes, I agree  
Besides SQL and Kolab, what backend do we support that would be  
considered read/write?