//! MySQL's convenience aliases: the family's types with the dialect named once, in the path.
//!
//! An alias is not a new type, so a value crosses between the two spellings by assignment:
//!
//! ```
//! use ingraph::comparison::sql::{SqlScalarComparison, mysql};
//!
//! let full = SqlScalarComparison::<i64, sqlx::MySql>::new();
//! let aliased: mysql::ScalarComparison<i64> = full;
//! assert!(aliased.is_empty());
//! ```
//!
//! What is on this shelf, and the rule that decides it, is `dialect_aliases!` in the parent module.
//!
//! [`MySqlDuration`](super::MySqlDuration) and [`MySqlDurationError`](super::MySqlDurationError) are
//! deliberately not on it: they already name the dialect, so an alias here would stutter, and one
//! that dropped the prefix would be a name the other two modules have nothing to match.
dialect_aliases!;
/// `SqlDurationComparison` on MySQL — a `TIME` column.
///
/// Outside `dialect_aliases!` because the kind is not on all three dialects: SQLite has no duration,
/// and its module says so rather than offering a name for one.
pub type DurationComparison<V> = SqlDurationComparison;