The optional mysql.ndb_replication table is used to specify 
binlogging and replication slave behaviour on a per-table basis.

The primary key of the table is the {db, table_name, server_id} triple.

This allows every table to have different binlog flags (updated only, 
log updates as writes) and different conflict handling at every server
if desired. Server Id 0 acts as a generic 'all server_ids' wildcard.

However, for large schemata, managing an individual row for each table
becomes a burden.

This feature introduces wildcards on the db and table_name columns
of the ndb_replication primary key.

The normal SQL LIKE wildcards (% - match zero or more characters, 
_ - match one character) are supported at any position in the db
or table_name columns.  A warning is given if the best match for
a particular table is ambiguous.

This allows simpler management of large schemata using conflict 
detection etc.

ndb_rpl_rep_error has been enhanced to give coverage of the
enhanced wildcard support.

(Hopefully) final recommit with ndb_table_guard.h file-id from 7.2