> We do sync form history on Android -- it was one of the first things I ever
> wrote as a MoCo employee. Collection "forms", only columns are "key" and
> "value" IIRC.
Huh, that fell out of my brain. So then… two of three platforms.
> I don't understand how "the name search-history" makes sense. This could
> identify a single record by guid, but the forms record format only stores one
> key=value pair.
Take a look: each record has a unique GUID, a name (always “search-history” for
searches), and a value (the search term).
This is true both in the DB and on the server. Obviously we store way more data
in the DB.
{collection: "forms", name: "searchbar-history", value: "sqlite case folding",
id: "zc/azbfecEuYy6kE", sortindex: 0}
{collection: "forms", name: "searchbar-history", value: "it's science fact",
id: "yPJnpKct+0K7LpS3", sortindex: 0}
> I think separating search history from forms in general is an excellent idea.
> Off the top, geotagging search history might be useful; it's probably not
> useful for forms.
Good point.
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
