October 11, 2016 at 11:14 am
Rune Bivrin (10/11/2016)
Ed Wagner (10/11/2016)
Okay, that's a little weird. Microsoft has updated the language to allow syntactically incorrect SQL based on popular habits. I see why they did it, but I don't agree with it.Oh, it's been like that for a long time. The same applies when initializing arrays in C#, by the way. Quite handy, if you ask me, and completely benign.
Yes, unusual but harmless and useful.
It's not partticularly new, either.
There was a language that allowed redundant commas in the 60s, I can't remember what it was called though and suspect it hasn't survived; I'm pretty sure it wasn't Algol 58, Jovial, Algol 60, Cobol, Coral or PL/1 and I don't think it was LISP but it might have been one of the Fortran versions (there were a lot of non-standard Fortrans back then) or something rather less mainstream (there were lots of languages in those days, and part of my job from 1 Oct 67 to 31 Mar 69 was doing a survey of the language features of as many programming languages as I could get infornmation on, and I was surprised by how many languages there were and how much of them included bizarre and esoteric stuff).
Tom
October 11, 2016 at 1:31 pm
Freaky. Did not expect that.
October 11, 2016 at 2:55 pm
TomThomson (10/11/2016)
Rune Bivrin (10/11/2016)
Ed Wagner (10/11/2016)
Okay, that's a little weird. Microsoft has updated the language to allow syntactically incorrect SQL based on popular habits. I see why they did it, but I don't agree with it.Oh, it's been like that for a long time. The same applies when initializing arrays in C#, by the way. Quite handy, if you ask me, and completely benign.
Yes, unusual but harmless and useful.
It's not partticularly new, either.
There was a language that allowed redundant commas in the 60s, I can't remember what it was called though and suspect it hasn't survived; I'm pretty sure it wasn't Algol 58, Jovial, Algol 60, Cobol, Coral or PL/1 and I don't think it was LISP but it might have been one of the Fortran versions (there were a lot of non-standard Fortrans back then) or something rather less mainstream (there were lots of languages in those days, and part of my job from 1 Oct 67 to 31 Mar 69 was doing a survey of the language features of as many programming languages as I could get infornmation on, and I was surprised by how many languages there were and how much of them included bizarre and esoteric stuff).
IBM OS JCL allowed varying numbers of commas in disk space allocation statements. Many jobs were aborted when a missing comma requested space allocation in cylinders instead in (intended) tracks and the space was not available.
October 12, 2016 at 1:19 am
TomThomson (10/11/2016)
Rune Bivrin (10/11/2016)
Ed Wagner (10/11/2016)
Okay, that's a little weird. Microsoft has updated the language to allow syntactically incorrect SQL based on popular habits. I see why they did it, but I don't agree with it.Oh, it's been like that for a long time. The same applies when initializing arrays in C#, by the way. Quite handy, if you ask me, and completely benign.
Yes, unusual but harmless and useful.
It's not partticularly new, either.
There was a language that allowed redundant commas in the 60s, I can't remember what it was called though and suspect it hasn't survived; I'm pretty sure it wasn't Algol 58, Jovial, Algol 60, Cobol, Coral or PL/1 and I don't think it was LISP but it might have been one of the Fortran versions (there were a lot of non-standard Fortrans back then) or something rather less mainstream (there were lots of languages in those days, and part of my job from 1 Oct 67 to 31 Mar 69 was doing a survey of the language features of as many programming languages as I could get infornmation on, and I was surprised by how many languages there were and how much of them included bizarre and esoteric stuff).
I think redundant commas we2r allowed in Algol 60 or perhaps COBOL. I think these were called 'noise words'.
October 13, 2016 at 7:35 am
Hi
The question had been placed here, but I cannot find it right now.
Here is the connect issue - https://connect.microsoft.com/SQLServer/feedback/details/273348/trailing-comma-allowed-in-create-table
You can add one comma "," in the end, but not more, and your create statement will pass successfully.
Igor Micev,My blog: www.igormicev.com
October 25, 2016 at 2:30 am
Easy one, thanks.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 2, 2016 at 10:05 am
Well that's a new one on me...
- Damian
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply