On 2017-01-19 13:14, Ann Harrison wrote:
>> On Jan 19, 2017, at 1:46 AM, Dmitry Yemanov
>> wrote:
>>
>> 19.01.2017 00:51, Ann Harrison wrote:
>>>
>>> In what universe does that make sense? The field is NOT NULL.
>>> You're storing NULL in it. That's an error.
>>
>>
On 2017-01-19 11:03, Adriano dos Santos Fernandes wrote:
> On 19/01/2017 07:07, Mark Rotteveel wrote:
>> Does the standard actually allow having an insert with null (or any
>> other value for that matter) for a GENERATED ALWAYS AS IDENTITY (I
>> don't
>> have a copy of the SQL standard at hand
On 2017-01-19 11:35, Adriano dos Santos Fernandes wrote:
> On 19/01/2017 08:22, Dimitry Sibiryakov wrote:
>> 19.01.2017 11:03, Adriano dos Santos Fernandes wrote:
>>
>>> c) If for some n, some underlying column of the column referenced by
>>> the
>>> CN contained
>>> in the n-th ordinal
> On Jan 19, 2017, at 1:46 AM, Dmitry Yemanov wrote:
>
> 19.01.2017 00:51, Ann Harrison wrote:
>>
>> In what universe does that make sense? The field is NOT NULL. You're
>> storing NULL in it. That's an error.
>
> I'd say it depends. What about a BEFORE trigger
On 19/01/2017 08:22, Dimitry Sibiryakov wrote:
> 19.01.2017 11:03, Adriano dos Santos Fernandes wrote:
>
>> c) If for some n, some underlying column of the column referenced by the
>> CN contained
>> in the n-th ordinal position in is an identity
>> column whose descriptor includes an
>>
19.01.2017 11:03, Adriano dos Santos Fernandes wrote:
> c) If for some n, some underlying column of the column referenced by the
> CN contained
> in the n-th ordinal position in is an identity
> column whose descriptor includes an
> indication that values are generated by default, then if
On 19/01/2017 07:07, Mark Rotteveel wrote:
> On 2017-01-18 23:38, Adriano dos Santos Fernandes wrote:
>> Ann, I assigned it to me based on Dimitry S. comment.
>>
>> After your comment, I edited the case to reflect the standard.
> Does the standard actually allow having an insert with null (or any
On 2017-01-18 23:38, Adriano dos Santos Fernandes wrote:
> Ann, I assigned it to me based on Dimitry S. comment.
>
> After your comment, I edited the case to reflect the standard.
Does the standard actually allow having an insert with null (or any
other value for that matter) for a GENERATED
19.01.2017 00:51, Ann Harrison wrote:
>
> In what universe does that make sense? The field is NOT NULL. You're
> storing NULL in it. That's an error.
I'd say it depends. What about a BEFORE trigger converting input NULL to
something valid before storing?
Dmitry
Ann, I assigned it to me based on Dimitry S. comment.
After your comment, I edited the case to reflect the standard.
Adriano
Em 18/01/2017 19:51, Ann Harrison escreveu:
> On Jan 18, 2017, at 11:17 AM, Gerhard S (JIRA)
> wrote:
>>
>> Insert NULL into identity column
On Jan 18, 2017, at 11:17 AM, Gerhard S (JIRA) wrote:
>
> Insert NULL into identity column with auth generated value
> --
>
> Key: CORE-5460
> URL:
11 matches
Mail list logo