On Fri, May 24, 2013 at 11:04 AM, Thomas Thrainer <[email protected]>wrote:
> > > > On Fri, May 24, 2013 at 10:23 AM, Guido Trotter <[email protected]>wrote: > >> >> >> >> On Fri, May 24, 2013 at 10:18 AM, Thomas Thrainer <[email protected]>wrote: >> >>> The Text backend now parses network UUID (comma separated) and >>> serializes them in the same form. >>> The test data is adapted to the new format. >>> >>> >> Would it make sense to have it at the end and optional, as Klaus did for >> other additions to the text backend he had, so old text backend data is not >> broken? >> >> Are there a lot of text data files around (except tests)? > We have a small secret stash of those, yes. :) > I'd prefer to break backwards compatibility for internal and test stuff, > as it's easy to update the (test-)data, and it simplifies the code. Also, > especially for the text backend, what would happen when we add another > field? How to decide which one was actually specified if just one was? This > would just postpone the problem until then... > > Oh, well, the idea there would be that you can't have the only the last without the semi-last. eg: name|info1|info2 is ok as is name|info1|info2|info3 or name|info1|info2|info3|info4 or name|info1|info2||info4 but not just name|info1|info2|info4 Thanks, Guido
