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
I love Simple. Data and I hope it doesn't die.
I am curious about something. I am playing with dynamic objects and not using models.
If I update a table like this:
db.Mytable.UpdateById(formRow);
Sometimes there are items in the data object (formRow) that are missing from the table. Only a couple at the most. I can remove these like this:
formRow.Remove(KeyName);
But is there any point? Simple.Data seems to be able to handle the mismatches.
Is it good practice to remove them? I would assume that I should only ever include cols that are being updated. But is it really necessary?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I love Simple. Data and I hope it doesn't die.
I am curious about something. I am playing with dynamic objects and not using models.
If I update a table like this:
Sometimes there are items in the data object (formRow) that are missing from the table. Only a couple at the most. I can remove these like this:
But is there any point? Simple.Data seems to be able to handle the mismatches.
Is it good practice to remove them? I would assume that I should only ever include cols that are being updated. But is it really necessary?
The text was updated successfully, but these errors were encountered: