anchor.diff:    /// You can tell moor which tables your query is going to affect by using the
     /// [updates] parameter. Query-streams running on any of these tables will
     /// then be re-run.
  -  @protected
  -  @visibleForTesting
     Future<int> customInsert(String query,
         {List<Variable> variables = const [], Set<TableInfo> updates}) {
       return _customWrite(
  
positive.code:   /// you can also set the [updateKind] parameter to [UpdateKind.delete] or
    /// [UpdateKind.update]. This is optional, but can improve the accuracy of
    /// query updates, especially when using triggers.
    @protected
    @visibleForTesting
    Future<int> customUpdate(
      String query, {
      List<Variable> variables = const [],
  
negative.code:   /// See also:
    ///  - the documentation on [aggregate expressions](https://moor.simonbinder.eu/docs/getting-started/expressions/#aggregate)
    ///  - the documentation on [group by](https://moor.simonbinder.eu/docs/advanced-features/joins/#group-by)
    JoinedSelectStatement<T, R> selectOnly<T extends Table, R extends DataClass>(
      TableInfo<T, R> table, {
      bool distinct = false,
  