You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One use case is the bulk conversion of dates in a known though ambiguous structure into parsed components. For example, if a date to be processed was expressed as "10/8/1972", under normal circumstances it would be ambiguous. But, if you could additionally inform the processor that the date is expressed as "DD/MM/YYYY", then it could be parsed without problem. One user has expressed a need for this because it would assist with their need to parse dates into columns without having to return to a source database and re-execute an export & to express dates in ISO.
The text was updated successfully, but these errors were encountered:
One use case is the bulk conversion of dates in a known though ambiguous structure into parsed components. For example, if a date to be processed was expressed as "10/8/1972", under normal circumstances it would be ambiguous. But, if you could additionally inform the processor that the date is expressed as "DD/MM/YYYY", then it could be parsed without problem. One user has expressed a need for this because it would assist with their need to parse dates into columns without having to return to a source database and re-execute an export & to express dates in ISO.
The text was updated successfully, but these errors were encountered: