Re: [Fofredux-devel] unknown column feed.latitude (upgrade issues)

[Kevin <ke...@dr...>]

>> So, what have we done so far that breaks FoF compatiblity?  I guess I'=
ll
>> have to install it and see.  Removing or renaming the "read" column
>> definitly will break it.  We could set a "compatiblity flag" that will
>> keep the "read" column in sync with the read/unread tags.  There are
>> very
>> few places where the read column is altered, so it's not too difficult
>> to
>> do.
>
> The problem is, if we switch to tags for state, FOF won't update that
> and will *only* update 'read,' which means changes made in FOF won't be
> picked up by us.

Okay, so it's not just supporting a downgrade path back to FoF, but also
running them in parallel.  So, the plus for doing this is making it easie=
r
for existing FoF users to try out FoFr.  The downside is we wait a few
revs before converting the read column to a tag.

--=20
Kevin