MssqlSchemaCheck class abstract final

Compares generated bindings against the live database.

This is what replaces migrations here. An ORM's migration makes the schema match the code; the direction is reversed in a DB-first package, so the counterpart is not changing anything but reporting the gap before a deploy finds it.

Properties

hashCode → int

The hash code for this object.

no setter, inherited

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

toString() → String

A string representation of this object.

inherited

Operators

operator ==(Object other) → bool

The equality operator.

inherited

Static Methods

compare(MssqlTableBinding<Object?> binding, MssqlTableSchema table) → MssqlSchemaReport

Compares one binding against a schema already in hand.

matchesFingerprint(MssqlTableBinding<Object?> binding, MssqlTableSchema table) → bool

The cheap version: has anything at all changed for binding?

verify(MssqlConnection connection, {required List<MssqlTableBinding<Object?>> bindings}) → Future<MssqlSchemaReport>

Reports how bindings differ from what connection actually has.

verifySnapshot(MssqlConnection connection, MssqlSchemaSnapshot snapshot, {bool includeViews = true}) → Future<MssqlSchemaReport>

Reports how the live database differs from snapshot.