Goodbye SELECT .

PeterK
Xpert

Heh - I didn't realize this but it turns out SELECT . is valid SQL in 7.0.

In 7.1 it generates a syntax error.

I only know this because one of our user's had a view with a . column (it was a typo). But now I'm curious whether . is actually meant to be supported by the SQL Standard. And, no, I will not even attempt to read the Standard.

1 ACCEPTED SOLUTION

ChristianGfK
Contributor

That seems related to this change in 7.1:

https://www.exasol.com/support/browse/EXASOL-2871

 
  •  
    A dot without any digits on either side used to be parsed as zero but now is not. So 'select . as ZERO' is no longer allowed.

 

View solution in original post

5 REPLIES 5

ChristianGfK
Contributor

That seems related to this change in 7.1:

https://www.exasol.com/support/browse/EXASOL-2871

 
  •  
    A dot without any digits on either side used to be parsed as zero but now is not. So 'select . as ZERO' is no longer allowed.

 

View solution in original post

exa-Matze
Team Exasol
Team Exasol

Hi @PeterK ,

 

the "." must not be used in identifiers according to the SQL standard. The "." is used for qualification, only.
Maybe there was a small bug in V7.0 which we fixed with V7.1, but I am not aware of this 😛 
I am quite sure that Exasol V6.x did not support this.

 

If you like, please create a ticket for our support for investigation, but I am 99% sure that this is an intended behavior 😉 

exa-GeorgD
Team Exasol
Team Exasol

Just for completeness sake 😎:

PeterK
Xpert

No need for a ticket ... I was only curious 🙂

exa-Chris
Community Manager
Community Manager

@exa-Matze said, even I should know this, but I doubt that 😁. Let me check and come back with a good answer. He said it was a bug that it was supported. But I will get that confirmed.

Connecting Customers, Partners, Prospects and Exasolians is my passion. Apart from that I cycle, listen to music, and try to understand what all those technical discussions really mean...