Tim Nevels writes: >On Aug 27, 2016, at 2:00 PM, Arnaud de Montard wrote: > >> 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.
4D does support the datetime data type when the field is created using SQL commands. It will behave like a date field when referencing it with 4D commands, but since it actually contains the time part too, you can get a 'timestamp' by using CAST(myDateTimeField as VARCHAR) in your SQL select statement. Tom Benedict Optum This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ********************************************************************** 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] **********************************************************************
