[Xapian-tickets] [Xapian] #53: Xapian::Fields

[Xapian]

#53: Xapian::Fields
-------------------------+-------------------------------
 Reporter:  Olly Betts   |             Owner:  Olly Betts
     Type:  enhancement  |            Status:  closed
 Priority:  lowest       |         Milestone:  1.5.0
Component:  Library API  |           Version:  SVN trunk
 Severity:  minor        |        Resolution:  fixed
 Keywords:               |        Blocked By:
 Blocking:               |  Operating System:  All
-------------------------+-------------------------------
Changes (by Olly Betts):

 * status:  assigned => closed
 * resolution:   => fixed
 * milestone:  1.4.x => 1.5.0

Comment:

 > I think we should chose a very compact storage scheme for the built-in
 field support (rather than XML or JSON or ...) because if people want a
 particular standard format, they can use an external library to
 serialise/unserialise it, whereas if they want a very compact format,
 there aren't many options.

 Since then [https://en.wikipedia.org/wiki/Protocol_Buffers protocol
 buffers] has emerged as a good option for this.  This uses a schema so you
 don't end up storing the field names used explicitly in every document,
 and a it's also extensible - you can add new fields without invalidating
 existing data.

 I think we should just suggest protocol buffers as a good option in the
 documentation.  It doesn't seem feasible to fully integrate support as
 from what I've seen typically code is generated from the schema, so it
 seems the encoding and decoding really needs to be handled from the
 application code which I've done in
 [b02984d631043ad04b3720a7869def0b813b5047].  I'll also adjust the "Getting
 Started" guide to recommend it.
-- 
Ticket URL: <https://trac.xapian.org/ticket/53#comment:13>
Xapian <https://xapian.org/>
Xapian