[logon] forthcoming revision of [incr tsdb()] database schema

[Stephan Oepen]

dear LOGON co-developers and users,

over the past few weeks, i finally completed and validated (to some
degree) the extensions to the [incr tsdb()] database schema that i
had announced last fall (see below).

as always, when the database schema changes, all skeletons will
need to be updated, as [incr tsdb()] will read old profiles but will
refuse to write to any revision of the database schema than the
current one.

for skeletons that are part of the LOGON tree, i have applied the
update.  for anyone with local skeletons, you will have to do this
yourselves.  this time, the update is simple: just copy in the new
‘relations’ file into each skeleton directory.  the latest version of
the master ‘relations’ file is available in the LOGON tree as

  lingo/lkb/src/tsdb/skeletons/english/Relations

i would like to encourage all LOGON users to ‘make update’ in
their $LOGONROOT directory and, if need be, also make sure
to copy the new ‘relations’ file (which should have 9746 bytes)
into your local skeletons.  please test typical use patterns and
let me know in case you notice something surprising.

—unrelated to the update of the database schema, please note
that i have just updated the LOGON tree with regards to which
version of the ERG is included by default: ‘lingo/erg/’ points to
the near-final 1212 release candidate of the ERG now.

happy easter!  oe


On Wed, Oct 31, 2012 at 1:05 AM, Stephan Oepen <oe at ifi.uio.no> wrote:
> colleagues,
>
> just a heads-up: i am planning on releasing a new version of the
> [incr tsdb()] database schema later this week.  this new revision
> adds a number of fields (and moderately reinterprets one or two
> existing ones), to provide the setup for forest-based treebanking.
>
> as with every schema revision, [incr tsdb()] will continue to read
> old profiles, but the new code will only support writing to profiles
> with the new schema.  in other words, all skeletons will need to
> be updated to the schema.  for data that is maintaines as part of
> the LOGON tree (mostly english by now), i will make the changes.
> but anyone maintaining their own skeletons will need to be aware
> of this update, and synchronize their getting the new code (i.e.
> updating their LOGON tree) to also dropping in the new scheme
> to their skeletons then.
>
> here are some instructions on this topic i had emailed when i
> last revised the database schema:
>
>   http://lists.emmtee.net/archives/logon/2011/000119.html
>
> assuming you applied those changes back then, this time it will
> be sufficient to just drop in the new ‘relations’ file (once it has
> been released, and the [incr tsdb()] and and run-time binaries
> support it).
>
> more on all this later in the week, i hope!  if you happen to be
> in the middle of something critical and would rather not think
> about database schema updates for a little while, it might be a
> good idea to bring your LOGON tree up-to-date /now/, before
> i commit the changes related to the schema revision.
>
> best wishes, oe