Hi,
Zoltan Boszormenyi írta:
Jan Wieck írta:
On 12/5/2005 1:03 PM, Zoltan Boszormenyi wrote:
Jan Wieck írta:
On 12/4/2005 5:10 PM, Zoltan Boszormenyi wrote:
I found this in the SQL2003 draft:
"
4.14.7 Identity columns
... An identity column has a start value, an increment, a maximum
Jan Wieck írta:
On 12/5/2005 1:03 PM, Zoltan Boszormenyi wrote:
Jan Wieck írta:
On 12/4/2005 5:10 PM, Zoltan Boszormenyi wrote:
I found this in the SQL2003 draft:
"
4.14.7 Identity columns
... An identity column has a start value, an increment, a maximum
value, a minimum value,
and a c
On 12/5/2005 1:03 PM, Zoltan Boszormenyi wrote:
Jan Wieck írta:
On 12/4/2005 5:10 PM, Zoltan Boszormenyi wrote:
I found this in the SQL2003 draft:
"
4.14.7 Identity columns
... An identity column has a start value, an increment, a maximum
value, a minimum value,
and a cycle option. ...
"
Jan Wieck írta:
On 12/4/2005 5:10 PM, Zoltan Boszormenyi wrote:
I found this in the SQL2003 draft:
"
4.14.7 Identity columns
... An identity column has a start value, an increment, a maximum
value, a minimum value,
and a cycle option. ...
"
The exact properties of a sequence. It would be
I think nobody would object to implementing support for the SQL2003
syntax. Most of that would be providing all the values that will get
forwarded into the internal sequence generation during CREATE TABLE.
Someone also pointed out on IRC the other day that Oracle and DB2 list
'identity' as the
On Dec 5, 2005, at 9:50 , Jan Wieck wrote:
If we had to pick any magic value I would vote for skipping 666 in
all sequence generators and use that.
What about 13?
Michael Glaesemann
grzm myrealbox com
---(end of broadcast)---
TIP 3: Have y
On 12/4/2005 5:10 PM, Zoltan Boszormenyi wrote:
I found this in the SQL2003 draft:
"
4.14.7 Identity columns
... An identity column has a start value, an increment, a maximum value,
a minimum value,
and a cycle option. ...
"
The exact properties of a sequence. It would be a good idea to be a
Zoltan Boszormenyi wrote:
I found this in the SQL2003 draft:
"
4.14.7 Identity columns
... An identity column has a start value, an increment, a maximum
value, a minimum value,
and a cycle option. ...
And that section says nothing at all about using 0 as a magic value. All
it says i
Jan Wieck írta:
On 12/3/2005 4:23 PM, Zoltan Boszormenyi wrote:
Hi!
I would like to add an entry to PostgreSQL 8.2 TODO:
- Extend SERIAL to a full-featured auto-incrementer type.
To achieve this, the following three requirements should be fulfilled:
1. The statement parser should be able to
Am Sonntag, den 04.12.2005, 08:52 +0100 schrieb Zoltan Boszormenyi:
> OK, I admit I haven't read the SQL standards on this matter.
>
> Tino Wildenhain írta:
>
...
> A SERIAL type has the assumption that its value starts at a low value
> (1) and
> is increasing. Or is there a type modifier keywor
OK, I admit I haven't read the SQL standards on this matter.
Tino Wildenhain írta:
Am Samstag, den 03.12.2005, 22:23 +0100 schrieb Zoltan Boszormenyi:
Hi!
I would like to add an entry to PostgreSQL 8.2 TODO:
- Extend SERIAL to a full-featured auto-incrementer type.
To achieve this, the fo
Zoltan Boszormenyi wrote:
Andrew Dunstan írta:
Zoltan Boszormenyi wrote:
Hi!
I would like to add an entry to PostgreSQL 8.2 TODO:
- Extend SERIAL to a full-featured auto-incrementer type.
I can't see this item on the TODO list at all. Where exactly did you
find it?
That's why I w
Zoltan Boszormenyi wrote:
> Peter Eisentraut ?rta:
>
> >Josh Berkus wrote:
> >
> >
> >>I believe that our SERIAL/SEQUENCE stuff is already in compliance
> >>with the SQL standard for sequences (in SQL03). Why would we change
> >>it?
> >>
> >>
> >
> >Because your belief is wrong, but Zoltan
Peter Eisentraut írta:
Josh Berkus wrote:
I believe that our SERIAL/SEQUENCE stuff is already in compliance
with the SQL standard for sequences (in SQL03). Why would we change
it?
Because your belief is wrong, but Zoltan's proposal is not getting is
closer.
OK, what does the
Andrew Dunstan írta:
Zoltan Boszormenyi wrote:
Hi!
I would like to add an entry to PostgreSQL 8.2 TODO:
- Extend SERIAL to a full-featured auto-incrementer type.
I can't see this item on the TODO list at all. Where exactly did you
find it?
That's why I wanted it ADDed... ;-)
Best reg
On 12/3/2005 4:23 PM, Zoltan Boszormenyi wrote:
Hi!
I would like to add an entry to PostgreSQL 8.2 TODO:
- Extend SERIAL to a full-featured auto-incrementer type.
To achieve this, the following three requirements should be fulfilled:
1. The statement parser should be able to handle this:
cre
Josh Berkus wrote:
> I believe that our SERIAL/SEQUENCE stuff is already in compliance
> with the SQL standard for sequences (in SQL03). Why would we change
> it?
Because your belief is wrong, but Zoltan's proposal is not getting is
closer.
--
Peter Eisentraut
http://developer.postgresql.org/
Zoltan,
> > I would like to add an entry to PostgreSQL 8.2 TODO:
> > - Extend SERIAL to a full-featured auto-incrementer type.
I believe that our SERIAL/SEQUENCE stuff is already in compliance with the
SQL standard for sequences (in SQL03). Why would we change it?
--
--Josh
Josh Berkus
Agli
Zoltan Boszormenyi wrote:
Hi!
I would like to add an entry to PostgreSQL 8.2 TODO:
- Extend SERIAL to a full-featured auto-incrementer type.
I can't see this item on the TODO list at all. Where exactly did you
find it?
cheers
andrew
---(end of broadcast)
Am Samstag, den 03.12.2005, 22:23 +0100 schrieb Zoltan Boszormenyi:
> Hi!
>
> I would like to add an entry to PostgreSQL 8.2 TODO:
> - Extend SERIAL to a full-featured auto-incrementer type.
>
> To achieve this, the following three requirements should be fulfilled:
>
> 1. The statement parser sh
Hi!
I would like to add an entry to PostgreSQL 8.2 TODO:
- Extend SERIAL to a full-featured auto-incrementer type.
To achieve this, the following three requirements should be fulfilled:
1. The statement parser should be able to handle this:
create table x (
id serial(N),
...
);
and behi
21 matches
Mail list logo
