Tickets :: Comment on [#12617] Most drivers don't implement 'fetch

* Your Email Address
* Spam protection	Enter the letters below: .__..__.. .. ..__. [__][__]\|\/\|\|\/\|\| \| \| \|\| \|\| \|\| \|\|__\
Comment	>>> 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?
Attachment
Watch this ticket