anchor.diff:  tables_of(Key) ->
       Schema = get_schema(Key),
       [ Tab || {table, Tab, _Opts} <- Schema ] ++
  -	?schematool_tables.
  +	schematool_tables().
  +
  +schematool_tables() ->
  +    ?schematool_tables.
  +
  +schematool_table_type() ->
  +    disc_copies.
   
   %% Migration from K0 to K1:
   %%
  
positive.code: %% - traverse schematool_changelog for this instead!
  
  current_schema() ->
      atomic(
        mnesia:transaction(
  	fun() ->
  
negative.code: %%% Description : 
  %%% Created : 22 Jan 2014 by Thomas Lindgren <>
  
  %% Schematool status
  %% - initialize schema db
  %% - generate db.schema -> db.schema.term via a
  %%   toolchain (because epp is a joke at the
  %%   expense of mainkind)
  %% - load db.schema.term into db
  %% - migrate between schemas using
  %%   * schematool generates migration actions
  %%       UNFINISHED - these need to be marshalled
  %%   * schematool_backup acts as a wrapper,
  %%     including rollback on failure (distributed!)
  %% - UNFINISHED
  %%   * previous attempts at schema management should
  %%     be removed, see below
  %%
  %% However, note that migration can be time consuming
  %% in some cases, e.g., that a lot of data need to be
  %% rewritten and/or copied. 
  %%
  %% NOTE: to run schematool, see ../bin/schematool.pl
  %%   (Also see Makefile for WF or erlmail.)
  %%
  %% This module is the start of schema processing once we
  %% have the schema module compiled and generated.
  