should Temporals be indexed natively or as [sortable] ISO/JSON strings in IndexedDb?

[kaizhu256]

if indexed as [sortable] ISO/JSON strings, what about ZonedInstant timezones?

fyi BigInt, which are indexed natively, have the following comparison-priority in IndexedDb (w3c/IndexedDB#231):

• BigInts compare greater than Number and less than everything else
• No type coercion between BigInt and Number; they are simply
  distinct, unrelated keys, even if mathematically equal
• No BigInt autoIncrement support--53 bits should be enough for anyone

[littledan]

To clarify, BigInt isn't permitted as a key in IndexedDB; the proposal you link to was not accepted.

[kaizhu256]

i see... so we shouldn't expect native support for Temporals either and treat them as [sortable] strings in IndexedDb?

[kaizhu256]

also, what would be the default sort-behavior for Temporals (and BigInt) in javascript Array? would Temporals sort like strings? would BigInt sort like the rejected IndexedDb proposal?