Matthew Draper

> I think having our own clear delimiter between "this is the version part" and "this is the digest part" might be best? > I like `docker@sha1:f199bc812a7d7c770139fe8f67203010e103d0f8` :+1: To me...

@rbgrouleff as a slight side-track from the specifics of this issue, for general API-utility purposes, I'm interested in the circumstances that lead you to need to hand-sanitize a LIMIT clause....

Some of the Node API indirection in here feels rather unfortunate -- especially `Document.node_attribute`. I understand that mutations are insurmountable, but for readonly traversal, can we instead expect some baseline...

I have a broad concern here around whether it's reasonable to assume that migrations will only affect a single schema. That feels like an apartment-centric assumption, so I'm inclined to...

> Would you explain why the latter "two signed 32-bit integers" is preferred over the current "single signed 64-bit integer" implementation? I don't feel like this question has been answered...

> Note that many clients make an exception for POST, and will use GET to follow a 302 redirect in that case. I think this is probably worth specific discussion....

I haven't taken the time to actually invent examples, but my recollection is that ordering of left joins can affect the query results (at least, I have strong memories that...

I agree adding a clarification seems helpful, though I am wary that this weights the bulk of the method description to the already-unusual case of a non-block argument 🤔 I...

I think this overlaps with #39968, which sits near the very top of my shame pile of super-valuable PRs I need to take the time to review and merge. It's...

> using an AS::Duration as a where argument directly To clarify, this is just specifically in the described context where it's currently doing the integer thing. When used in the...