Table of Contents

Namespace YndigoBlue.Velocity

The YndigoBlue.Velocity namespace is the root of the Velocity API — a unified data access framework for .NET that targets IBM DB2, Microsoft SQL Server, MySQL, Oracle, PostgreSQL, SQLite, and Teradata Vantage through a single consistent interface.

All database operations flow through the Manager class, which exposes a uniform API surface regardless of the underlying database. Rather than generating a generic lowest-common-denominator abstraction, Velocity maps each operation to the most appropriate native implementation for the target database — so features like full-text search, geospatial queries, and schema introspection work correctly on every supported platform without conditional code in your application.

The API is structured around three layers. The data layer (YndigoBlue.Velocity.Data) encapsulates database-specific connection parameters and adaptors, with one sub-namespace per supported database (YndigoBlue.Velocity.Data.DB2, YndigoBlue.Velocity.Data.MySql, YndigoBlue.Velocity.Data.Oracle, YndigoBlue.Velocity.Data.PostgreSql, YndigoBlue.Velocity.Data.SqlServer, YndigoBlue.Velocity.Data.Sqlite, YndigoBlue.Velocity.Data.Teradata). The model layer (YndigoBlue.Velocity.Model) provides the domain objects — schemas, tables, queries, and records — that are used uniformly across all databases. The engine layer (YndigoBlue.Velocity.Engine) executes operations against the connected database by translating model objects into the correct SQL dialect.

Queries are constructed using the fluent Query builder with support from over 70 strongly-typed function wrappers in YndigoBlue.Velocity.Functions. Results can be returned as raw result sets or bound directly to typed C# objects via Record<T>. Schema definitions are expressed declaratively in XML, JSON, or YAML, and can be created, updated, and introspected at runtime through Manager.

Namespace Description
YndigoBlue.Velocity.Attributes Attributes for controlling data binding behaviour on C# model classes
YndigoBlue.Velocity.Data Database connection classes and adaptors, with one sub-namespace per supported database
YndigoBlue.Velocity.Constraints Constraint types for use in schema definitions: PrimaryKey, ForeignKey, Unique, Check, Default
YndigoBlue.Velocity.Engine The Manager class — the primary entry point for all database operations
YndigoBlue.Velocity.Enums Enumerations used across the API
YndigoBlue.Velocity.Exceptions Strongly-typed exception classes for every error condition Velocity can raise
YndigoBlue.Velocity.Functions Over 70 strongly-typed SQL function wrappers for use in queries
YndigoBlue.Velocity.Model Core domain model
YndigoBlue.Velocity.Utils Internal utility and helper classes

Namespaces

YndigoBlue.Velocity.Attributes
YndigoBlue.Velocity.Constraints
YndigoBlue.Velocity.Data
YndigoBlue.Velocity.Engine
YndigoBlue.Velocity.Enums
YndigoBlue.Velocity.Exceptions
YndigoBlue.Velocity.Functions
YndigoBlue.Velocity.Interfaces
YndigoBlue.Velocity.Model
YndigoBlue.Velocity.Utils