Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
What's the best way to store a date in a smart contract?

In developing for blockchain it's important to save space, so it seems better to store the dates using 32-bit timestamps instead of 64-bit. But blockchain is also meant to be "forever", and the dates will fit in the 32-bit integers only till the year 2038. So what is considered the best practice: using 64-bit integers (to future-proof the contracts) or 32-bit (to save space)?

This question was imported from Telegram Chat: https://t.me/tondev/45383

Votes Newest


0 Answers
one year ago
one year ago