{"database": "github", "table": "issue_comments", "rows": [["https://github.com/pydata/xarray/pull/5045#issuecomment-832821013", "https://api.github.com/repos/pydata/xarray/issues/5045", 832821013, "MDEyOklzc3VlQ29tbWVudDgzMjgyMTAxMw==", 1217238, "2021-05-05T16:11:37Z", "2021-05-05T16:11:37Z", "MEMBER", "> I revised the pre-assignment checks. In my opinion xr.align is not so helpful when checking that the dimension sizes and coordinates are consistent, because it doesn't fail when the dimension size of the two Datasets is different, but the coordinate of the second Dataset is a subset of the first one.\r\n\r\nCould you kindly elaborate on this issue, maybe with a specific example?\r\n\r\n> If, despite the checks, an error occurs during the assignment, e.g. due to a type error, and the dataset has been updated already partially, the user is informed about this.\r\n\r\n`np.can_cast` with `casting='unsafe` can check this. It sounds like this would probably be something good to add to our checks :)", "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", null, 833778859]], "columns": ["html_url", "issue_url", "id", "node_id", "user", "created_at", "updated_at", "author_association", "body", "reactions", "performed_via_github_app", "issue"], "primary_keys": ["id"], "primary_key_values": ["832821013"], "units": {}, "query_ms": 0.4291320074116811}