2015-06-03 15:36 GMT-03:00 Stephan Eggermont <[email protected]>: > On 03-06-15 20:15, Esteban A. Maringolo wrote: >> >> I refer Postgres datatypes because I find them to have a good criteria >> based on a huge user base and because is what raised the issue I'm >> dealing with now. > > > SQL databases are well-known to have ignored the standards for > dealing with times and dates for decades to make it difficult to > switch to a competitor.
Sorry, but never heard of this intentional ignorance, particularly coming from PostgreSQL. Nonetheless, I had to deal with stupid issues in Oracle 7i-11g, but that's another story. Regarding standards, I mentioned the ISO 8601 where I haven't seen a case where a plain date comes with a timezone offset. > For performance reasons you'll probably often want to map to smallint value > objects. And lose the date abstraction the database provides me with? It is up to the database how to optimize the store of its datatypes. Regards! Esteban A. Maringolo
