> Le 25 août 2016 à 21:45, Tim Nevels <[email protected]> a écrit : > >> [...] > > Peter is right, 4D has always stored dates internally as 3 “fields”. Each > “field” is 2 bytes in size or an integer. Hence, maximum year value of > 32,732.
Hi Tim, since v11 I think this is wrong, see the number of bytes of some 4D fields: <http://screencast.com/t/eRDzgw0BNZ9> Both date and hour types are 8 bytes whereas if we where still in the before-v11-situation, date should be 6 (2*3) and hour should be 4 (same as a longint, which explains the selection to array(hourField;longintArray)). This (added to some strange things happening in SQL queries on date fields, example <http://forums.4d.fr/Post/FR/16272092/0/0/>) makes me think that this 8 byte storage is a timestamp (date+hour), still not "revealed" by 4D for compatibility reasons. Pure speculation, of course. -- Arnaud de Montard ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
