× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. May 2018

Re: m/d/yyyy string to yyyymmdd decimal in SQL

Yeah, I see your point, Rob. Especially since other single-digit combinations (such as 392018) don't parse at all.  To your point, I think most people will store the extra zero; you'll typically only see the 3/9/2018 with the delimiter.

Honestly, I wasn't expecting it to work as well as it did (although with Alan I shouldn't be surprised, his code is always excellent); I was just playing with an edge condition to see that would happen.


On 5/7/2018 11:57 AM, Rob Berendt wrote:
I think most people would have the internal zero as in 12082018 for
2018-12-28. The leading zero, as in 1282018 for 2018-01-28 is where most
people would assume the optional part would come in. Most likely from an
incorrect method used to convert from decimal to character.
However, if you just have to be a literalist, I can see your point and he
should have called it mddyyyy. If for no other reason than to have
avoided this thread (and probably the only reason).



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.