Postgres has special date/time input value called 'allballs'
1–8 of 8 posts
Re: Postgres has special date/time input value called 'allballs'
#2Re: Postgres has special date/time input value called 'allballs'
#3I think balls is a military term for "00"
Re: Postgres has special date/time input value called 'allballs'
#4Under the century section it notes:
"The first century starts at 0001-01-01 00:00:00 AD, although they did not know it at the time. This definition applies to all Gregorian calendar countries. There is no century number 0, you go from -1 century to 1 century. If you disagree with this, please write your complaint to: Pope, Cathedral Saint-Peter of Roma, Vatican."
I chuckle imagining someone in the Vatican mail room tossing aside one letter a year related to this.
Re: Postgres has special date/time input value called 'allballs'
#5My favorite (kind of related) little gem from the postgresql documentation is from the century section of EXTRACT, date_part: https://www.postgresql.org/docs/9.5/static/functions-datetim... Under the century section it notes: "The first century starts at 0001-01-01 00:00:00 AD, although they did not know it at the time. This definition applies to all Gregorian calendar countries. There is no century number 0, you go…
Re: Postgres has special date/time input value called 'allballs'
#6Re: Postgres has special date/time input value called 'allballs'
#7Re: Postgres has special date/time input value called 'allballs'
#8My favorite (kind of related) little gem from the postgresql documentation is from the century section of EXTRACT, date_part: https://www.postgresql.org/docs/9.5/static/functions-datetim... Under the century section it notes: "The first century starts at 0001-01-01 00:00:00 AD, although they did not know it at the time. This definition applies to all Gregorian calendar countries. There is no century number 0, you go…
"Hi. I have a Toyota Carola 2012, and can't get blutooth working..."