Quartz.NET Weasel integration for Firebird - the ADO.NET job store's tables as a Weasel model, applied by db-apply, resources setup or at startup; Quartz Scheduling Framework for .NET
Install
| Product | Versions |
|---|---|
| .NET |
README
Quartz.Weasel.Firebird
Quartz.Weasel.Firebird hands a Firebird job store's schema
to Weasel. Weasel then creates and migrates Quartz's tables at startup and from
JasperFx's db-apply, db-assert, db-patch and resources commands.
Installation
dotnet add package Quartz.Weasel.Firebird
Usage
builder.Services.AddQuartz(q => q.UsePersistentStore(store =>
{
store.UseFirebird(connectionString);
store.UseWeaselForFirebird();
}));
- Firebird 3, 4 and 5, through FirebirdSql.Data.FirebirdClient (
UseFirebird). - The tables are add-only: columns, indexes and foreign keys you added to them are kept.
- No lock: every statement is guarded, and nodes applying at once read the schema again.
- Firebird has no schemas, so a table prefix with a dot is refused.
- Names are at most 31 bytes on Firebird 3, so the table prefix is at most 6 characters. For a database only
Firebird 4 or later opens, set
MaxIdentifierLength = 63. - A UTF8 database needs a page size of 16384.
Weasel.Firebird was contributed to Weasel in JasperFx/weasel#666. Thanks to the JasperFx maintainers for merging it.
Documentation
https://www.quartz-scheduler.net/documentation/quartz-4.x/packages/weasel.html
Changes from Previous Version
Adoption Assessment
A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.