EventFlow.Sql
0.29.1973
Prefix Reserved
See the version list below for details.
dotnet add package EventFlow.Sql --version 0.29.1973
NuGet\Install-Package EventFlow.Sql -Version 0.29.1973
<PackageReference Include="EventFlow.Sql" Version="0.29.1973" />
paket add EventFlow.Sql --version 0.29.1973
#r "nuget: EventFlow.Sql, 0.29.1973"
// Install EventFlow.Sql as a Cake Addin #addin nuget:?package=EventFlow.Sql&version=0.29.1973 // Install EventFlow.Sql as a Cake Tool #tool nuget:?package=EventFlow.Sql&version=0.29.1973
Generic SQL support for EventFlow
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET Framework | net451 is compatible. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
NuGet packages (3)
Showing the top 3 NuGet packages that depend on EventFlow.Sql:
| Package | Downloads |
|---|---|
|
EventFlow.MsSql
# EventFlow  ``` $ dotnet add package EventFlow ``` EventFlow is a basic CQRS+ES framework designed to be easy to use. Have a look at our [getting started guide](https://geteventflow.net/getting-started/), the [do’s and don’ts](https://geteventflow.net/additional/dos-and-donts/) and the [FAQ](https://geteventflow.net/additional/faq/). Alternatively, join our [Discord](https://discord.gg/QfgNPs5WxR) server to engage with the community. Its hopefully getting a reboot to kickstart the upcoming release of v1. ## Features * **Easy to use**: Designed with sensible defaults and implementations that make it easy to create an example application * **Highly configurable and extendable**: EventFlow uses interfaces for every part of its core, making it easy to replace or extend existing features with custom implementation * **No use of threads or background workers** * **MIT licensed** Easy to understand and use license for enterprise ## Versions Development of version 1.0 has started and is mainly braking changes regarding changes related to replacing EventFlow types with that of Microsoft extension abstractions, mainly `IServiceProvider` and `ILogger<>`. The following list key characteristics of each version as well as its related branches (not properly configured yet). * `1.x` Represents the next iteration of EventFlow that aligns EventFlow with the standard packages for .NET. Releases here will only support .NET Standard, .NET Core and .NET versions 6+ going forward. - Released - Still development - Not all projects migrated yet Read the [migration guide](https://geteventflow.net/migrations/v0-to-v1/) to view the full list of breaking changes as well as recommendations on how to migrate. ### Documentation Version 1.x documentation has been pulled into this repository in order to have the code and documentation closer together and have the documentation updated in the same pull-requests as any code changes. The compiled version of the documentation is available at https://geteventflow.net/. ### NuGet package status - 🟢 ported - 💚 newly added to 1.0 - 🟠 not yet ported to 1.0 - 💀 for packages that are removed as part of 1.0 (see the [migration guide](https://geteventflow.net/migrations/v0-to-v1/) for details) Projects - 🟢 `EventFlow` - 🟠 `EventFlow.AspNetCore` - 💀 `EventFlow.Autofac` - 💀 `EventFlow.DependencyInjection` - 🟠 `EventFlow.Elasticsearch` - 🟢 `EventFlow.EntityFramework` - 🟠 `EventFlow.EventStores.EventStore` - 🟢 `EventFlow.Hangfire` - 🟢 `EventFlow.MongoDB` - 🟢 `EventFlow.MsSql` - 💀 `EventFlow.Owin` - 🟢 `EventFlow.PostgreSql` - 💚 `EventFlow.Redis` - 🟠 `EventFlow.RabbitMQ` - 🟢 `EventFlow.Sql` - 🟢 `EventFlow.SQLite` - 🟢 `EventFlow.TestHelpers` ### Branches - `develop-v1`: Development branch, pull requests should be done here - `release-v1`: Release branch, merge commits are done to this branch from `develop-v1` to create releases. Typically each commit represents a release * `0.x` (legacy) The current stable version of EventFlow and has been the version of EventFlow for almost six years. 0.x versions have .NET Framework support and limited support to the Microsoft extension packages through extra NuGet packages. Feature and bug fix releases will still be done while there's interest in the community. ### Branches - `develop-v0`: Development branch, pull requests should be done here - `release-v0`: Release branch, merge commits are done to this branch from `develop-v0` to create releases. Typically each commit represents a release ### Documentation Version 0.x documentation is (although a bit outdated) is live at https://docs.geteventflow.net/. |
|
|
EventFlow.PostgreSql
# EventFlow  ``` $ dotnet add package EventFlow ``` EventFlow is a basic CQRS+ES framework designed to be easy to use. Have a look at our [getting started guide](https://geteventflow.net/getting-started/), the [do’s and don’ts](https://geteventflow.net/additional/dos-and-donts/) and the [FAQ](https://geteventflow.net/additional/faq/). Alternatively, join our [Discord](https://discord.gg/QfgNPs5WxR) server to engage with the community. Its hopefully getting a reboot to kickstart the upcoming release of v1. ## Features * **Easy to use**: Designed with sensible defaults and implementations that make it easy to create an example application * **Highly configurable and extendable**: EventFlow uses interfaces for every part of its core, making it easy to replace or extend existing features with custom implementation * **No use of threads or background workers** * **MIT licensed** Easy to understand and use license for enterprise ## Versions Development of version 1.0 has started and is mainly braking changes regarding changes related to replacing EventFlow types with that of Microsoft extension abstractions, mainly `IServiceProvider` and `ILogger<>`. The following list key characteristics of each version as well as its related branches (not properly configured yet). * `1.x` Represents the next iteration of EventFlow that aligns EventFlow with the standard packages for .NET. Releases here will only support .NET Standard, .NET Core and .NET versions 6+ going forward. - Released - Still development - Not all projects migrated yet Read the [migration guide](https://geteventflow.net/migrations/v0-to-v1/) to view the full list of breaking changes as well as recommendations on how to migrate. ### Documentation Version 1.x documentation has been pulled into this repository in order to have the code and documentation closer together and have the documentation updated in the same pull-requests as any code changes. The compiled version of the documentation is available at https://geteventflow.net/. ### NuGet package status - 🟢 ported - 💚 newly added to 1.0 - 🟠 not yet ported to 1.0 - 💀 for packages that are removed as part of 1.0 (see the [migration guide](https://geteventflow.net/migrations/v0-to-v1/) for details) Projects - 🟢 `EventFlow` - 🟠 `EventFlow.AspNetCore` - 💀 `EventFlow.Autofac` - 💀 `EventFlow.DependencyInjection` - 🟠 `EventFlow.Elasticsearch` - 🟢 `EventFlow.EntityFramework` - 🟠 `EventFlow.EventStores.EventStore` - 🟢 `EventFlow.Hangfire` - 🟢 `EventFlow.MongoDB` - 🟢 `EventFlow.MsSql` - 💀 `EventFlow.Owin` - 🟢 `EventFlow.PostgreSql` - 💚 `EventFlow.Redis` - 🟠 `EventFlow.RabbitMQ` - 🟢 `EventFlow.Sql` - 🟢 `EventFlow.SQLite` - 🟢 `EventFlow.TestHelpers` ### Branches - `develop-v1`: Development branch, pull requests should be done here - `release-v1`: Release branch, merge commits are done to this branch from `develop-v1` to create releases. Typically each commit represents a release * `0.x` (legacy) The current stable version of EventFlow and has been the version of EventFlow for almost six years. 0.x versions have .NET Framework support and limited support to the Microsoft extension packages through extra NuGet packages. Feature and bug fix releases will still be done while there's interest in the community. ### Branches - `develop-v0`: Development branch, pull requests should be done here - `release-v0`: Release branch, merge commits are done to this branch from `develop-v0` to create releases. Typically each commit represents a release ### Documentation Version 0.x documentation is (although a bit outdated) is live at https://docs.geteventflow.net/. |
|
|
EventFlow.SQLite
# EventFlow  ``` $ dotnet add package EventFlow ``` EventFlow is a basic CQRS+ES framework designed to be easy to use. Have a look at our [getting started guide](https://geteventflow.net/getting-started/), the [do’s and don’ts](https://geteventflow.net/additional/dos-and-donts/) and the [FAQ](https://geteventflow.net/additional/faq/). Alternatively, join our [Discord](https://discord.gg/QfgNPs5WxR) server to engage with the community. Its hopefully getting a reboot to kickstart the upcoming release of v1. ## Features * **Easy to use**: Designed with sensible defaults and implementations that make it easy to create an example application * **Highly configurable and extendable**: EventFlow uses interfaces for every part of its core, making it easy to replace or extend existing features with custom implementation * **No use of threads or background workers** * **MIT licensed** Easy to understand and use license for enterprise ## Versions Development of version 1.0 has started and is mainly braking changes regarding changes related to replacing EventFlow types with that of Microsoft extension abstractions, mainly `IServiceProvider` and `ILogger<>`. The following list key characteristics of each version as well as its related branches (not properly configured yet). * `1.x` Represents the next iteration of EventFlow that aligns EventFlow with the standard packages for .NET. Releases here will only support .NET Standard, .NET Core and .NET versions 6+ going forward. - Released - Still development - Not all projects migrated yet Read the [migration guide](https://geteventflow.net/migrations/v0-to-v1/) to view the full list of breaking changes as well as recommendations on how to migrate. ### Documentation Version 1.x documentation has been pulled into this repository in order to have the code and documentation closer together and have the documentation updated in the same pull-requests as any code changes. The compiled version of the documentation is available at https://geteventflow.net/. ### NuGet package status - 🟢 ported - 💚 newly added to 1.0 - 🟠 not yet ported to 1.0 - 💀 for packages that are removed as part of 1.0 (see the [migration guide](https://geteventflow.net/migrations/v0-to-v1/) for details) Projects - 🟢 `EventFlow` - 🟠 `EventFlow.AspNetCore` - 💀 `EventFlow.Autofac` - 💀 `EventFlow.DependencyInjection` - 🟠 `EventFlow.Elasticsearch` - 🟢 `EventFlow.EntityFramework` - 🟠 `EventFlow.EventStores.EventStore` - 🟢 `EventFlow.Hangfire` - 🟢 `EventFlow.MongoDB` - 🟢 `EventFlow.MsSql` - 💀 `EventFlow.Owin` - 🟢 `EventFlow.PostgreSql` - 💚 `EventFlow.Redis` - 🟠 `EventFlow.RabbitMQ` - 🟢 `EventFlow.Sql` - 🟢 `EventFlow.SQLite` - 🟢 `EventFlow.TestHelpers` ### Branches - `develop-v1`: Development branch, pull requests should be done here - `release-v1`: Release branch, merge commits are done to this branch from `develop-v1` to create releases. Typically each commit represents a release * `0.x` (legacy) The current stable version of EventFlow and has been the version of EventFlow for almost six years. 0.x versions have .NET Framework support and limited support to the Microsoft extension packages through extra NuGet packages. Feature and bug fix releases will still be done while there's interest in the community. ### Branches - `develop-v0`: Development branch, pull requests should be done here - `release-v0`: Release branch, merge commits are done to this branch from `develop-v0` to create releases. Typically each commit represents a release ### Documentation Version 0.x documentation is (although a bit outdated) is live at https://docs.geteventflow.net/. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last updated |
|---|---|---|
| 1.2.0 | 317 | 13 days ago |
| 1.1.0 | 2,130 | 3 months ago |
| 1.0.5007 | 649 | 4 months ago |
| 1.0.5004-alpha | 1,102 | 10 months ago |
| 1.0.5003-alpha | 7,877 | 6/21/2023 |
| 1.0.5002-alpha | 806 | 11/11/2022 |
| 1.0.5001-alpha | 1,217 | 3/15/2022 |
| 1.0.4748-alpha | 11,585 | 9/9/2021 |
| 1.0.4617-alpha | 902 | 6/11/2021 |
| 0.84.4 | 3,515 | 4 months ago |
| 0.83.4713 | 468,625 | 9/7/2021 |
| 0.82.4684 | 1,728 | 8/30/2021 |
| 0.82.4659 | 8,968 | 6/17/2021 |
| 0.81.4483 | 131,188 | 12/14/2020 |
| 0.80.4377 | 57,329 | 10/1/2020 |
| 0.79.4216 | 60,495 | 5/13/2020 |
| 0.78.4205 | 2,084 | 5/11/2020 |
| 0.77.4077 | 36,893 | 12/10/2019 |
| 0.76.4014 | 7,634 | 10/19/2019 |
| 0.75.3970 | 3,802 | 9/12/2019 |
| 0.74.3948 | 6,971 | 7/1/2019 |
| 0.73.3933 | 3,117 | 6/11/2019 |
| 0.72.3914 | 5,067 | 5/28/2019 |
| 0.71.3834 | 5,908 | 4/17/2019 |
| 0.70.3824 | 2,576 | 4/11/2019 |
| 0.69.3772 | 5,366 | 2/12/2019 |
| 0.68.3728 | 12,619 | 12/3/2018 |
| 0.67.3697 | 4,035 | 10/14/2018 |
| 0.66.3673 | 2,767 | 9/28/2018 |
| 0.65.3664 | 6,245 | 9/22/2018 |
| 0.64.3598 | 5,195 | 8/27/2018 |
| 0.63.3581 | 2,836 | 8/7/2018 |
| 0.62.3569 | 2,274 | 7/5/2018 |
| 0.61.3524 | 2,741 | 6/26/2018 |
| 0.60.3490 | 2,111 | 6/18/2018 |
| 0.59.3396 | 2,348 | 5/23/2018 |
| 0.58.3377 | 2,074 | 5/13/2018 |
| 0.57.3359 | 2,157 | 4/30/2018 |
| 0.56.3328 | 1,785 | 4/24/2018 |
| 0.55.3323 | 1,751 | 4/24/2018 |
| 0.54.3261 | 1,934 | 2/25/2018 |
| 0.53.3204 | 1,900 | 1/25/2018 |
| 0.52.3178 | 1,789 | 11/2/2017 |
| 0.51.3155 | 1,747 | 10/25/2017 |
| 0.50.3124 | 1,813 | 10/21/2017 |
| 0.49.3031 | 2,195 | 9/7/2017 |
| 0.48.2937 | 2,094 | 7/11/2017 |
| 0.47.2894 | 1,763 | 6/28/2017 |
| 0.46.2886 | 1,864 | 5/29/2017 |
| 0.45.2877 | 1,876 | 5/28/2017 |
| 0.44.2832 | 2,297 | 5/12/2017 |
| 0.43.2806 | 1,616 | 5/5/2017 |
| 0.42.2755 | 2,061 | 5/2/2017 |
| 0.41.2727 | 2,019 | 4/27/2017 |
| 0.40.2590 | 5,212 | 3/30/2017 |
| 0.39.2553 | 2,181 | 1/16/2017 |
| 0.38.2454 | 2,214 | 12/2/2016 |
| 0.37.2424 | 2,353 | 11/8/2016 |
| 0.36.2315 | 3,180 | 10/18/2016 |
| 0.35.2247 | 2,269 | 9/6/2016 |
| 0.34.2221 | 2,040 | 8/23/2016 |
| 0.33.2190 | 1,985 | 8/16/2016 |
| 0.32.2163 | 2,064 | 7/4/2016 |
| 0.31.2106 | 2,087 | 6/30/2016 |
| 0.30.2019 | 2,466 | 6/16/2016 |
| 0.29.1973 | 3,746 | 4/19/2016 |
| 0.28.1852 | 2,087 | 4/5/2016 |
| 0.27.1765 | 5,598 | 2/25/2016 |
| 0.26.1714 | 2,111 | 2/20/2016 |
Breaking: `IAggregateRoot` has some breaking changes. If these methods aren't
used (which is considered the typical case), then the base class
`AggregateRoot<,,>` will automatically handle it
- `CommitAsync` has an additional `ISnapshotStore` parameter. If you don't
use snapshot aggregates, then you can safely pass `null`
- `LoadAsync` is a new method that lets the aggregate control how its
loaded fromt the event- and snapshot stores
New core feature:** EventFlow now support snapshot creation for aggregate
roots. The EventFlow documentation has been updated to include a guide on
how to get started using snapshots. Snapshots are basically an opt-in optimized
method for handling long-lived aggregate roots. Snapshot support in EventFlow
introduces several new elements, read the documentation to get an overview.
Currently EventFlow offers the following snapshot stores
- In-memory
- Microsoft SQL Server
New: The `IAggregateStore` is introduced, which provides a cleaner interface
for manipulating aggregate roots. The most important method is the
`UpdateAsync` which allows easy updates to aggregate roots without the need
for a command and command handler
- `LoadAsync`
- `UpdateAsync`
- `StoreAsync`
New: `IEventStore` now supports loading events from a specific version using
the new overload of `LoadEventsAsync` that takes a `fromEventSequenceNumber`
argument
New: `IMsSqlDatabaseMigrator` now has a overloaded method named
`MigrateDatabaseUsingScripts` that takes an `IEnumerable<SqlScript>`
enabling specific scripts to be used in a database migration
New: Added suport to use EventStore persistence with connection strings
instead IPs only
Obsolete: The following aggregate related methods on `IEventStore` has been
marked as obsolete in favor of the new `IAggregateStore`. The methods will be
removed at some point in the future
- `LoadAggregateAsync`
- `LoadAggregate`