On 27-8-2013 20:12, Adriano dos Santos Fernandes wrote:
On 27/08/2013 15:06, Leyne, Sean wrote:
I think an USING clause would be a great addition:
GENERATED BY DEFAULT AS IDENTITY [USING SEQUENCE name]
What do you think?
What Sequence (name) would be used if the USING was omitted?
A
On 28/08/2013 08:15, Dimitry Sibiryakov wrote:
Any column properties must be managed as the column's properties.
Yes, at least in this case. I found the missing clauses in the standard:
alter column definition ::=
ALTER [ COLUMN ] column name alter column action
alter column action ::=
27.08.2013 23:47, Leyne, Sean wrote:
While I agree with your questions, I don't agree that Identity would be a
consideration for cluster/cloud architecture.
Identity/Sequences are a poor fit for such usage modes, GUIDs/UUIDs are much
more appropriate, since the chances of same GUID being
On 27/08/2013 18:15, Dimitry Sibiryakov wrote:
27.08.2013 22:06, Adriano dos Santos Fernandes wrote:
Why do a future version will go against the SQL standard?
Does standard explicitly mention that identity's internal sequence must be
user-manipulatible? Does it say that in must be the same
28.08.2013 13:08, Adriano dos Santos Fernandes wrote:
It's clear a sequence. It even supports the parameters:
Even if sequence and identity column has similar attributes, it doesn't mean
that they
are directly related.
Author of CORE-4191 wants to set generator name for identity to
On 27-8-2013 20:22, Adriano dos Santos Fernandes wrote:
The user issue is about managing the internal generator.
You can do it now, but you need to discover its internal name.
Why complicate things?
Identity columns allows the use to put manually generated values. So the
ability to manage
I think an USING clause would be a great addition:
GENERATED BY DEFAULT AS IDENTITY [USING SEQUENCE name]
What do you think?
What Sequence (name) would be used if the USING was omitted?
Sean
--
Learn the
On 27/08/2013 13:30, Leyne, Sean wrote:
I think an USING clause would be a great addition:
GENERATED BY DEFAULT AS IDENTITY [USING SEQUENCE name]
What do you think?
What Sequence (name) would be used if the USING was omitted?
A generated one, like now and like happens with constraints and
27.08.2013 20:03, Adriano dos Santos Fernandes wrote:
I think an USING clause would be a great addition:
GENERATED BY DEFAULT AS IDENTITY [USING SEQUENCE name]
What do you think?
Basically, I don't mind, but the behavior will be different from
constraints in regard to the already existing
On 27/08/2013 14:11, Dmitry Yemanov wrote:
27.08.2013 20:03, Adriano dos Santos Fernandes wrote:
I think an USING clause would be a great addition:
GENERATED BY DEFAULT AS IDENTITY [USING SEQUENCE name]
What do you think?
Basically, I don't mind, but the behavior will be different from
I think an USING clause would be a great addition:
GENERATED BY DEFAULT AS IDENTITY [USING SEQUENCE name]
What do you think?
What Sequence (name) would be used if the USING was omitted?
A generated one, like now and like happens with constraints and indexes.
Aren't IDENTITY
On 27/08/2013 14:11, Dmitry Yemanov wrote:
27.08.2013 20:03, Adriano dos Santos Fernandes wrote:
I think an USING clause would be a great addition:
GENERATED BY DEFAULT AS IDENTITY [USING SEQUENCE name]
What do you think?
Basically, I don't mind, but the behavior will be different
On 27/08/2013 15:06, Leyne, Sean wrote:
I think an USING clause would be a great addition:
GENERATED BY DEFAULT AS IDENTITY [USING SEQUENCE name]
What do you think?
What Sequence (name) would be used if the USING was omitted?
A generated one, like now and like happens with constraints
if firebird supported namespaces/schema AND longer identifiers, this would
be alot simpler...
On 27 August 2013 14:11, Leyne, Sean s...@broadviewsoftware.com wrote:
On 27/08/2013 14:11, Dmitry Yemanov wrote:
27.08.2013 20:03, Adriano dos Santos Fernandes wrote:
I think an USING
I think an USING clause would be a great addition:
GENERATED BY DEFAULT AS IDENTITY [USING SEQUENCE name]
What do you think?
What Sequence (name) would be used if the USING was omitted?
A generated one, like now and like happens with constraints and indexes.
Aren't IDENTITY
The user issue is about managing the internal generator.
You can do it now, but you need to discover its internal name.
Why complicate things?
Identity columns allows the use to put manually generated values. So the
ability to manage a sequence is a must-have.
And if a object can be managed,
On 27/08/2013 15:19, Leyne, Sean wrote:
I think an USING clause would be a great addition:
GENERATED BY DEFAULT AS IDENTITY [USING SEQUENCE name]
What do you think?
What Sequence (name) would be used if the USING was omitted?
A generated one, like now and like happens with constraints
27.08.2013 20:22, Adriano dos Santos Fernandes wrote:
The user issue is about managing the internal generator.
You can do it now, but you need to discover its internal name.
Why complicate things?
Complication is managing identity columns via generator. Every operation
should be
18 matches
Mail list logo