Skip to content
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

Interception should plug into CSpace #1

Closed
cocowalla opened this issue Oct 7, 2014 · 1 comment
Closed

Interception should plug into CSpace #1

cocowalla opened this issue Oct 7, 2014 · 1 comment

Comments

@cocowalla
Copy link

Similar to this one.

As it is now we can't use database column names that differ from the C# property names.

@jcachat
Copy link
Collaborator

jcachat commented Oct 19, 2014

This should be fixed now.

I had to implement it differently than how you did it in the other project. Changing to use CSpace caused issues in how my queries were being built and also caused issues with retrieving the parameter value if you have more than 1 DbContext created.

But the result should be the same and I added a test case to the example program I added earlier tonight to test it. The "RemappedEntityProp" property in the Account class is mapped to a database column name of "RemappedDBProp". Before the change, that blew up. With the change, it's now build the query correctly against the "RemappedDBProp" db column name and mapping the filter parameter value correctly.

Thanks for pointing this out. I had not hit this yet in my own use but I'm sure it was just a matter of time.

-John

@jcachat jcachat closed this as completed Nov 30, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants