-
Notifications
You must be signed in to change notification settings - Fork 302
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
Ignore() is ignored by FluentMapping #59
Comments
Looking deeper in the NPoco code I can see that it has something to do with Then in the I am having a hard time figuring out the logic behind this. As far as I am concerned, if a column is flagged as ignored then it should be truly ignored when SQL is built. |
I got it! I need to pass false into the second optional parameter of Adam, you might wanna clarify this fine point in your wiki to help other devs avoid a similar confusion. |
Hey, |
No need to change anything in the code itself, perhaps just make a point of explaining the importance of the Thanks for your quick response! |
2.2.45 has fixed the Ignore. It was not working when using the FluentMappings. It will always look at the ignore now. |
It looks like columns that are configured using the FluentMapping API to be ignored are included in the generated INSERT statement.
I have this class:
In my FluentMapping configuration I do this:
I have confirmed by putting a breakpoint inside the
IgnoreComplex
lambda that it returnstrue
for bothAdditionalData
andLineItems
(i.e. they should be ignored).However, the generated INSERT statement still contains both of these properties as if they were columns.
This also happens even if I explicitly Ignore() these properties in my
InvoiceHeaderMap
class.The text was updated successfully, but these errors were encountered: