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
Thread for discussion regarding supporting an EF Core store provider for better reporting/storage.
Selfishly, I'm only looking to support MS SQL but EF Core is nice in that it's supposed to be agnostic (or at least, support being agnostic). Perhaps defining what the interface should look like is a good place to start, as well as the "schema" that the ESENT database uses currently in vanilla pull server (which can be viewed using ESE Database Viewer.
Table schemas (mdb file)
The text was updated successfully, but these errors were encountered:
Thanks for kicking off this discussion and providing a starting point for the schema. Can you clarify, is your screenshot showing what the schema of the current ESENT database includes, or is that just a sample you're put together? Because all 3 entities have the same structure in your example.
It's supposed to be the MDB file (since I'm not using ESENT), but you're right--looks like a bug with the program, it's showing the exact same fields in each table 👎 I can try again, that's weird.
I've started a collaborative workspace on this wiki page that we can use to hash out some ideas. I've started with your schema above. We can use this ticket to "discuss" ideas and capture design in the wiki.
Thread for discussion regarding supporting an EF Core store provider for better reporting/storage.
Selfishly, I'm only looking to support MS SQL but EF Core is nice in that it's supposed to be agnostic (or at least, support being agnostic). Perhaps defining what the interface should look like is a good place to start, as well as the "schema" that the ESENT database uses currently in vanilla pull server (which can be viewed using ESE Database Viewer.
Table schemas (mdb file)
The text was updated successfully, but these errors were encountered: