Context Navigation

Changes between Initial Version and Version 1 of Ticket #37175, comment 2

initial	v1
1		Hello Tim! Thank you for taking the time to create the report. I understand your concerns and the issue that this raises for other backends. I agree we could improve this situation by providing. potentially, some hooks at the database backend layer, but I also think that many of the tests currently hardcoding the PKs could be re-worked to not use a PK at all, or at least not assume is an int.
	1	Hello Tim! Thank you for taking the time to create the report. I understand your concerns and the issue that this raises for other backends. I agree we could improve this situation by providing, potentially, some hooks at the database backend layer, but I also think that many of the tests currently hardcoding the PKs could be re-worked to not use a PK at all, or at least not assume is an int.
2	2
3	3	Right now we are prioritizing 6.1 beta work, but I'll commit to do a more informed triage/review of this ticket after beta (likely next week). I'm accepting it right now since the problem statement is real, but I'd like to evaluate other options for the solution, ideally a solution that would not require a `get_hardcoded_pk()`. Have you considered posting in the forum to see what our creative community can suggest?