Peter Brawley wrote,
"The earliest possible MySQL date is around 1000CE, so
you could not store geologic dates in MySQL date cols.
"Million years before present" is the geologic time
unit that would most likely cohere with other geo
databases, isn't it? Then the Cambrian would show up
around 580 m
David,
The earliest possible MySQL date is around 1000CE, so you could not
store geologic dates in MySQL date cols. "Million years before present"
is the geologic time unit that would most likely cohere with other geo
databases, isn't it? Then the Cambrian would show up around 580 mya, the
begi
If you want to represent 290 million years as an integer (290,000,000):
- An UNSIGNED INT can store 4,294,967,295
- A UNSIGNED BIGINT can store 18,446,744,073,709,551,615
In your schema, I'd use a start_period and end_period instead of a
varchar. It's easier to sort and do math on.
You could fac
