You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There should be an CreateIfNeeded method on the MsSqlEventStore that can be used to created the underlying database when it does not exists. This helps people to setup quickly.
The text was updated successfully, but these errors were encountered:
My 2c on this is to use the EF code first technology for MsSqlEventStore once it is out of CTP and into mainstream, it is perfect for this scenario as the schema never changes
I would rather not have to take a dependency on EF just to use ncqrs. I also don't think that there is enough to gain by moving to an ORM as the data access is simple enough. Of course this is just my 1c contribution to the thoughts on this.
I use EF Code First for my ReadModels. I think it will be very usefull to use it also for creating the EventStore. Another great thing is you have intellisense on your queries (Linq). This will prevent issues like issue #63. People who don't want to use EF can simply use the current eventStore with a script. Dependency injection should be the solution to this.
There should be an CreateIfNeeded method on the MsSqlEventStore that can be used to created the underlying database when it does not exists. This helps people to setup quickly.
The text was updated successfully, but these errors were encountered: