We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Before serialization I have a Linq value like:
{((i.CustomerInboundRef == value(InventoryManager.PutawayService+<>c__DisplayClass29_0).customerCartonRef) }
This generates a nice sql server query with parameterized values.
After serialization the Linq value becomes a literal: {(i.CustomerInboundRef == "30c8725f-d")}
This generates a non parameterized sql server query, and I believe prevents the query from being reused in Entity Framework query cache.
When we serialize and deserialize can we keep the variable reference, so that the query can be generated with parameterized values?
The text was updated successfully, but these errors were encountered:
Don't think so, cause the backend does not know the Class
Sorry, something went wrong.
No branches or pull requests
Before serialization I have a Linq value like:
{((i.CustomerInboundRef == value(InventoryManager.PutawayService+<>c__DisplayClass29_0).customerCartonRef) }
This generates a nice sql server query with parameterized values.
After serialization the Linq value becomes a literal: {(i.CustomerInboundRef == "30c8725f-d")}
This generates a non parameterized sql server query, and I believe prevents the query from being reused in Entity Framework query cache.
When we serialize and deserialize can we keep the variable reference, so that the query can be generated with parameterized values?
The text was updated successfully, but these errors were encountered: