EventFlow.MsSql
0.8.560
Prefix Reserved
See the version list below for details.
dotnet add package EventFlow.MsSql --version 0.8.560
NuGet\Install-Package EventFlow.MsSql -Version 0.8.560
<PackageReference Include="EventFlow.MsSql" Version="0.8.560" />
paket add EventFlow.MsSql --version 0.8.560
#r "nuget: EventFlow.MsSql, 0.8.560"
// Install EventFlow.MsSql as a Cake Addin #addin nuget:?package=EventFlow.MsSql&version=0.8.560 // Install EventFlow.MsSql as a Cake Tool #tool nuget:?package=EventFlow.MsSql&version=0.8.560
MSSQL 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. |
-
- EventFlow (= 0.8.560)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.0.5007 | 92 | 11/16/2024 |
1.0.5004-alpha | 547 | 5/23/2024 |
1.0.5003-alpha | 4,527 | 6/21/2023 |
1.0.5002-alpha | 323 | 11/11/2022 |
1.0.5001-alpha | 445 | 3/15/2022 |
1.0.4748-alpha | 10,019 | 9/9/2021 |
1.0.4617-alpha | 324 | 6/11/2021 |
0.84.4 | 78 | 11/16/2024 |
0.83.4713 | 385,664 | 9/7/2021 |
0.82.4684 | 551 | 8/30/2021 |
0.82.4659 | 5,851 | 6/17/2021 |
0.81.4483 | 113,948 | 12/14/2020 |
0.80.4377 | 40,304 | 10/1/2020 |
0.79.4216 | 8,033 | 5/13/2020 |
0.78.4205 | 703 | 5/11/2020 |
0.77.4077 | 30,371 | 12/10/2019 |
0.76.4014 | 4,121 | 10/19/2019 |
0.75.3970 | 2,449 | 9/12/2019 |
0.74.3948 | 4,194 | 7/1/2019 |
0.73.3933 | 1,630 | 6/11/2019 |
0.72.3914 | 3,641 | 5/28/2019 |
0.71.3834 | 2,548 | 4/17/2019 |
0.70.3824 | 897 | 4/11/2019 |
0.69.3772 | 1,512 | 2/12/2019 |
0.68.3728 | 9,004 | 12/3/2018 |
0.67.3697 | 1,426 | 10/14/2018 |
0.66.3673 | 1,187 | 9/28/2018 |
0.65.3664 | 4,367 | 9/22/2018 |
0.64.3598 | 3,562 | 8/27/2018 |
0.63.3581 | 1,151 | 8/7/2018 |
0.62.3569 | 1,407 | 7/5/2018 |
0.61.3524 | 1,196 | 6/26/2018 |
0.60.3490 | 1,104 | 6/18/2018 |
0.59.3396 | 1,188 | 5/23/2018 |
0.58.3377 | 1,232 | 5/13/2018 |
0.57.3359 | 1,225 | 4/30/2018 |
0.56.3328 | 1,057 | 4/24/2018 |
0.55.3323 | 1,044 | 4/24/2018 |
0.54.3261 | 1,017 | 2/25/2018 |
0.53.3204 | 1,177 | 1/25/2018 |
0.52.3178 | 1,079 | 11/2/2017 |
0.51.3155 | 982 | 10/25/2017 |
0.50.3124 | 995 | 10/21/2017 |
0.49.3031 | 1,476 | 9/7/2017 |
0.48.2937 | 1,322 | 7/11/2017 |
0.47.2894 | 1,074 | 6/28/2017 |
0.46.2886 | 1,130 | 5/29/2017 |
0.45.2877 | 1,066 | 5/28/2017 |
0.44.2832 | 1,719 | 5/12/2017 |
0.43.2806 | 1,102 | 5/5/2017 |
0.42.2755 | 1,070 | 5/2/2017 |
0.41.2727 | 1,056 | 4/27/2017 |
0.40.2590 | 4,169 | 3/30/2017 |
0.39.2553 | 1,197 | 1/16/2017 |
0.38.2454 | 1,260 | 12/2/2016 |
0.37.2424 | 1,369 | 11/8/2016 |
0.36.2315 | 2,116 | 10/18/2016 |
0.35.2247 | 1,333 | 9/6/2016 |
0.34.2221 | 1,063 | 8/23/2016 |
0.33.2190 | 1,072 | 8/16/2016 |
0.32.2163 | 1,109 | 7/4/2016 |
0.31.2106 | 1,143 | 6/30/2016 |
0.30.2019 | 1,465 | 6/16/2016 |
0.29.1973 | 2,753 | 4/19/2016 |
0.28.1852 | 1,097 | 4/5/2016 |
0.27.1765 | 4,714 | 2/25/2016 |
0.26.1714 | 1,225 | 2/20/2016 |
0.25.1695 | 1,127 | 2/15/2016 |
0.24.1563 | 1,481 | 1/25/2016 |
0.23.1470 | 1,782 | 12/5/2015 |
0.22.1393 | 2,046 | 11/19/2015 |
0.21.1312 | 1,327 | 10/26/2015 |
0.20.1274 | 1,130 | 10/22/2015 |
0.19.1225 | 1,152 | 10/19/2015 |
0.18.1181 | 1,538 | 10/7/2015 |
0.17.1134 | 1,250 | 9/28/2015 |
0.16.1120 | 1,228 | 9/27/2015 |
0.15.1057 | 1,204 | 9/24/2015 |
0.14.1051 | 1,194 | 9/23/2015 |
0.13.962 | 1,453 | 9/13/2015 |
0.12.891 | 1,161 | 9/4/2015 |
0.11.751 | 1,159 | 8/24/2015 |
0.10.642 | 1,179 | 8/17/2015 |
0.9.580 | 1,242 | 7/20/2015 |
0.8.560 | 1,188 | 5/29/2015 |
0.7.481 | 1,133 | 5/22/2015 |
0.6.456 | 1,163 | 5/18/2015 |
0.5.390 | 1,229 | 5/8/2015 |
0.4.353 | 1,231 | 5/5/2015 |
0.3.292 | 1,376 | 4/30/2015 |
Breaking: Remove _all_ functionality related to global sequence
numbers as it proved problematic to maintain. It also matches this
quote:
> Order is only assured per a handler within an aggregate root
> boundary. There is no assurance of order between handlers or
> between aggregates. Trying to provide those things leads to
> the dark side.
>> Greg Young
- If you use a MSSQL read store, be sure to delete the
`LastGlobalSequenceNumber` column during update, or set it to
default `NULL`
- `IDomainEvent.GlobalSequenceNumber` removed
- `IEventStore.LoadEventsAsync` and `IEventStore.LoadEvents` taking
a `GlobalSequenceNumberRange` removed
Breaking: Remove the concept of event caches. If you really need this
then implement it by registering a decorator for `IEventStore`
Breaking: Moved `IDomainEvent.BatchId` to metadata and created
`MetadataKeys.BatchId` to help access it
New: `IEventStore.DeleteAggregateAsync` to delete an entire aggregate
stream. Please consider carefully if you really want to use it. Storage
might be cheaper than the historic knowledge within your events
New: `IReadModelPopulator` is new and enables you to both purge and
populate read models by going though the entire event store. Currently
its only basic functionality, but more will be added
New: `IEventStore` now has `LoadAllEventsAsync` and `LoadAllEvents` that
enables you to load all events in the event store a few at a time.
New: `IMetadata.TimestampEpoch` contains the Unix timestamp version
of `IMetadata.Timestamp`. Also, an additional metadata key
`timestamp_epoch` is added to events containing the same data. Note,
the `TimestampEpoch` on `IMetadata` handles cases in which the
`timestamp_epoch` is not present by using the existing timestamp
Fixed: `AggregateRoot<>` now reads the aggregate version from
domain events applied during aggregate load. This resolves an issue
for when an `IEventUpgrader` removed events from the event stream
Fixed: `InMemoryReadModelStore<,>` is now thread safe