-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to specify an optional SplitToTable configuration #29652
Comments
This issue is lacking enough information for us to be able to fully understand what is happening. Please attach a small, runnable project or post a small, runnable code listing that reproduces what you are seeing so that we can investigate. |
There it is:
Resulting query:
It works well in an environment where all records are created with the existence of the splittedtable at the beginning, but when you do mutation to your database adding some splittedtable after you already have records, its not possible to get results, unless executing some kind of script to create rows for every record in the new table during migration process. Is there any configuration for the split table, where I can inform that it may not have records? (Left join) |
@gabrielmatrella We will discuss. |
Duplicate of #27974 |
I need to configure fields in the splitted table as optional, to ef core prepare queries with left join instead inner, there is some way to achieve this now?
The resulting query:
EF Core version: 7.0.0
Database provider: (e.g. Npgsql)
The text was updated successfully, but these errors were encountered: