Huh. The Date data type in Databricks has a curious min/max value
Limits
The range of dates supported is June 23 -5877641 CE to July 11 +5881580 CE
For reference, homo sapiens appeared maybe -300,000 BCE so that's a pretty big range either way.
Setting June 23rd as the zero date though? There's gotta be some tie to the underlying data type representation that makes this make sense. -5.8M * 366 nets out to about -2.151 (bigint) and * 365 is -2.145M (int) so guessing that an int underneath.
Bill Fellows /
npub1c9…rp72p
2023-10-05 15:35:21
Author Public Key
npub1c9shmy8un2d3l0up6c9wcz6p2kkzw8v2u5mml5qpklqxhtpjturqzrp72pPublished at
2023-10-05 15:35:21Event JSON
{
"id": "480d4236c2f1a148ee2db91edc206d290bcd4c3dc7e893bf1a11d2c11f42f51b",
"pubkey": "c1617d90fc9a9b1fbf81d60aec0b4155ac271d8ae537bfd001b7c06bac325f06",
"created_at": 1696520121,
"kind": 1,
"tags": [
[
"proxy",
"https://dataplatform.social/users/billinkc/statuses/111183142697326915",
"activitypub"
]
],
"content": "Huh. The Date data type in Databricks has a curious min/max value\n\nLimits\n\nThe range of dates supported is June 23 -5877641 CE to July 11 +5881580 CE\n\nFor reference, homo sapiens appeared maybe -300,000 BCE so that's a pretty big range either way. \n\nSetting June 23rd as the zero date though? There's gotta be some tie to the underlying data type representation that makes this make sense. -5.8M * 366 nets out to about -2.151 (bigint) and * 365 is -2.145M (int) so guessing that an int underneath.",
"sig": "b8523464a18aad61b89e6a1d3cc796985f5d283b61f64d679f9bb2cd192bc9531674170d384ba136c7aa514787123cd8d7270e6c7a071584ba7822be6c974582"
}