jcelko212 32090 wrote:
>> THIS coming from the person that says he likes the MySQL "standard" of using YYYY-00-00 as the notation for whole years and YYYY-MM-00 for whole months. What a line of hooie. <<
The MySQL proposal is well understood and not something I made up locally. I'm forcing this kind of thing only because SQL Server does not have INTERVAL temporal datatypes. The nice part about this is my lookup table of date ranges can be quickly converted when SQL Server comes up to standard. You might also remember that I was the guy that wrote "LEFT OUTER JOIN" Versions of the old *= extended equality outer joins so that when Microsoft caught up the rest of the world, they could simply uncomment my code.
Understood but the trouble is that it violates the very ISO standards that you keep trumpeting about and, as of right now, there is no datatype that will support it as a date. It will be (at best) a CHAR(10) and contains formatting for readability. And, as of right now, it can't be used for interval calculations at all unless you modify the "00" parts of the string to something valid for such calculations.
p.s. You still owe me the ANSI or ISO standard/document number where it states your position of the YYYY-MM-DD format being the ONLY format supported in the "SQL Standard". 😉
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"If "pre-optimization" is the root of all evil, then what does the resulting no optimization lead to?"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)