You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2021/04/28 15:32:12 UTC

[GitHub] [arrow] emkornfield commented on pull request #10177: [Proposal] Add MONTH_DAY_NANO interval type

emkornfield commented on pull request #10177:
URL: https://github.com/apache/arrow/pull/10177#issuecomment-828552989


   > I know I was lobbying for nanosecond precision intervals, but given postgres and parquet both use millisecond precision, perhaps it would be best if Arrow followed the same model?
   
   I thought postgres used Microseconds not Milliseconds.  This is why the postgres struct there was 8 bytes for seconds/subseconds.  I actually liked the argument for having the finest grained available data available of other Arrow temporal types.  I'm not sure any alignment is going to be perfect.  Using this type in language specific concepts is already going to require a special type (e.g. there is nothing that seems to include all the fields together in the survey).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org