08.03.2016 21:00, Dimitry Sibiryakov wrote:
>
> Should I put it into tracker to let the change be documented as an
> incompatibility with
> previous versions?
Yes, please.
Dmitry
--
Transform Data into Opportunity.
A
08.03.2016 18:16, Dmitry Yemanov wrote:
> Looks OK to me.
Should I put it into tracker to let the change be documented as an
incompatibility with
previous versions?
--
WBR, SD.
--
Transform Data into Opportunity
08.03.2016 20:10, Dimitry Sibiryakov wrote:
>> Do you want to throw a syntax error from the parser or something more
>> intelligent like "duplicate constraint definitions are not allowed" from
>> DdlNodes?
>
> Standard syntax error from parser is the simplest solution:
>
>> SQL> create table t
08.03.2016 17:59, Dmitry Yemanov wrote:
> Do you want to throw a syntax error from the parser or something more
> intelligent like "duplicate constraint definitions are not allowed" from
> DdlNodes?
Standard syntax error from parser is the simplest solution:
> SQL> create table t (a integer no
08.03.2016 19:51, Dimitry Sibiryakov wrote:
> 08.03.2016 17:46, Dmitry Yemanov wrote:
>>> "create table t (a integer not null not null not null)" is a valid syntax
>>> or a bug?
>> I'd call it a bug. A very minor one for sure.
>
> Am I allowed to commit a fix?
Do you want to throw a syntax error
08.03.2016 17:46, Dmitry Yemanov wrote:
>> "create table t (a integer not null not null not null)" is a valid syntax or
>> a bug?
> I'd call it a bug. A very minor one for sure.
Am I allowed to commit a fix?
--
WBR, SD.
08.03.2016 17:24, Dimitry Sibiryakov wrote:
>
> "create table t (a integer not null not null not null)" is a valid syntax or
> a bug?
I'd call it a bug. A very minor one for sure.
Dmitry
--
Transform Data into Opportu
Hello, All.
"create table t (a integer not null not null not null)" is a valid syntax or
a bug?
--
WBR, SD.
--
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Ana