feat: Add schema selection support to compare method

[colonelpanic8]

Summary

This PR adds one_schema and two_schema parameters to the Comparer.compare() method, enabling comparison of specific database schemas rather than using the default schema.

Motivation

When working with PostgreSQL databases that use multiple schemas (e.g., a "railbird" schema instead of the default "public" schema), there was no way to specify which schema to compare. This feature is essential for projects that organize their database objects within named schemas.

Changes

• Added one_schema and two_schema parameters to Comparer.compare()
• Updated _get_db_info() to accept and pass schema parameter to inspectors
• Updated BaseInspector.inspect() abstract method signature to include schema parameter
• Updated all concrete inspectors to use the schema parameter when calling SQLAlchemy inspector methods:
  • TablesInspector
  • ColumnsInspector
  • PrimaryKeysInspector
  • ForeignKeysInspector
  • IndexesInspector
  • UniqueConstraintsInspector
  • CheckConstraintsInspector
  • EnumsInspector

Usage

from sqlalchemydiff.comparer import Comparer

comparer = Comparer.from_params(db_one_uri, db_two_uri)
result = comparer.compare(
    one_schema="my_schema",
    two_schema="my_schema",
)

Backward Compatibility

The schema parameters default to None, maintaining full backward compatibility with existing code. When None, SQLAlchemy uses the database's default schema behavior.

🤖 Generated with Claude Code