@@identity crisis?

@@identity crisis?

Post by John Brash » Sat, 03 Aug 1996 04:00:00



i don't know whether it's me or the dbms, but at least one of us is con-

defined on the table containing the identity column.

anyone know what's going on here?  the system is sybase 11.0 on an alpha
running digital unix 3.2 rev D.

j brasher
university of washington

trace follows:
---------------------------------------------------------------------------
1> create table dammit
2> (
3>       id     numeric(7) identity
4>      ,name   varchar(8)
5> )
6> go

1> create table nonsense
2> (
3>       name   varchar(8)
4> )
5> go

1> insert nonsense values ("foo")
2> insert nonsense values ("bar")
3> go

(1 row affected)
(1 row affected)

1> insert dammit values ("foo")
2> go

(1 row affected)


2> go

-----------------------------------------
                                        1 <---- ok.

(1 row affected)

1> alter table nonsense add primary key (name)
2> go

1> alter table dammit add foreign key (name) references nonsense (name)
2> go

1> insert dammit values ("bar")
2> go

(1 row affected)


2> go

-----------------------------------------
                                        0 <---- bummer.

(1 row affected)

1> select * from dammit
2> go
id         name    
---------- --------
         1 foo      
         2 bar      

(2 rows affected)

 
 
 

@@identity crisis?

Post by Tim Ng » Sat, 03 Aug 1996 04:00:00


We reported this bug to Sybase about 3 months ago.  I recently received the fix for it and it is
available for HP-UX. Other OS would get it somtimes in Aug.


> i don't know whether it's me or the dbms, but at least one of us is con-

> defined on the table containing the identity column.

> anyone know what's going on here?  the system is sybase 11.0 on an alpha
> running digital unix 3.2 rev D.

> j brasher
> university of washington

> trace follows:
> ---------------------------------------------------------------------------
> 1> create table dammit
> 2> (
> 3>       id     numeric(7) identity
> 4>      ,name   varchar(8)
> 5> )
> 6> go

> 1> create table nonsense
> 2> (
> 3>       name   varchar(8)
> 4> )
> 5> go

> 1> insert nonsense values ("foo")
> 2> insert nonsense values ("bar")
> 3> go

> (1 row affected)
> (1 row affected)

> 1> insert dammit values ("foo")
> 2> go

> (1 row affected)


> 2> go

> -----------------------------------------
>                                         1 <---- ok.

> (1 row affected)

> 1> alter table nonsense add primary key (name)
> 2> go

> 1> alter table dammit add foreign key (name) references nonsense (name)
> 2> go

> 1> insert dammit values ("bar")
> 2> go

> (1 row affected)


> 2> go

> -----------------------------------------
>                                         0 <---- bummer.

> (1 row affected)

> 1> select * from dammit
> 2> go
> id         name
> ---------- --------
>          1 foo
>          2 bar

> (2 rows affected)


 
 
 

@@identity crisis?

Post by LTCB Internationa » Tue, 06 Aug 1996 04:00:00



> i don't know whether it's me or the dbms, but at least one of us is con-

> defined on the table containing the identity column.

> anyone know what's going on here?  the system is sybase 11.0 on an alpha
> running digital unix 3.2 rev D.

> j brasher
> university of washington

> trace follows:
> ---------------------------------------------------------------------------
> 1> create table dammit
> 2> (
> 3>       id     numeric(7) identity
> 4>      ,name   varchar(8)
> 5> )
> 6> go

> 1> create table nonsense
> 2> (
> 3>       name   varchar(8)
> 4> )
> 5> go

> 1> insert nonsense values ("foo")
> 2> insert nonsense values ("bar")
> 3> go

> (1 row affected)
> (1 row affected)

> 1> insert dammit values ("foo")
> 2> go

> (1 row affected)


> 2> go

> -----------------------------------------
>                                         1 <---- ok.

> (1 row affected)

> 1> alter table nonsense add primary key (name)
> 2> go

> 1> alter table dammit add foreign key (name) references nonsense (name)
> 2> go

> 1> insert dammit values ("bar")
> 2> go

> (1 row affected)


> 2> go

> -----------------------------------------
>                                         0 <---- bummer.

> (1 row affected)

> 1> select * from dammit
> 2> go
> id         name
> ---------- --------
>          1 foo
>          2 bar

> (2 rows affected)This looks like a bug we've been experiencing on version 11.01 on

Solaris 2.4.  I'm told (but have not tested) that it is fixed in the next
release (11.011).  Has anyone tested this version?

Matthew Rock

 
 
 

@@identity crisis?

Post by Cipher Consulting Service » Wed, 07 Aug 1996 04:00:00



        This is on Sybase 11.0.1.

        We have been told that SYBASE has a EMERGENCY BUG-FIX for it,
        and we will be getting it in a day or so. And then we will
        test it.



> > i don't know whether it's me or the dbms, but at least one of us is con-

> > defined on the table containing the identity column.

> > anyone know what's going on here?  the system is sybase 11.0 on an alpha
> > running digital unix 3.2 rev D.

> > j brasher
> > university of washington

> > trace follows:
> > ---------------------------------------------------------------------------
> > 1> create table dammit
> > 2> (
> > 3>       id     numeric(7) identity
> > 4>      ,name   varchar(8)
> > 5> )
> > 6> go

> > 1> create table nonsense
> > 2> (
> > 3>       name   varchar(8)
> > 4> )
> > 5> go

> > 1> insert nonsense values ("foo")
> > 2> insert nonsense values ("bar")
> > 3> go

> > (1 row affected)
> > (1 row affected)

> > 1> insert dammit values ("foo")
> > 2> go

> > (1 row affected)


> > 2> go

> > -----------------------------------------
> >                                         1 <---- ok.

> > (1 row affected)

> > 1> alter table nonsense add primary key (name)
> > 2> go

> > 1> alter table dammit add foreign key (name) references nonsense (name)
> > 2> go

> > 1> insert dammit values ("bar")
> > 2> go

> > (1 row affected)


> > 2> go

> > -----------------------------------------
> >                                         0 <---- bummer.

> > (1 row affected)

> > 1> select * from dammit
> > 2> go
> > id         name
> > ---------- --------
> >          1 foo
> >          2 bar

> > (2 rows affected)This looks like a bug we've been experiencing on version 11.01 on
> Solaris 2.4.  I'm told (but have not tested) that it is fixed in the next
> release (11.011).  Has anyone tested this version?

> Matthew Rock

 
 
 

@@identity crisis?

Post by Jo Arne Lervi » Thu, 08 Aug 1996 04:00:00


This looks like a bug we've been experiencing on version 11.01 on

Quote:> Solaris 2.4.  I'm told (but have not tested) that it is fixed in the next
> release (11.011).  Has anyone tested this version?

We are running SQL Server/11.0.1/P/Sun_svr4/OS 5.4/EBF6417/OPT/Thu Jun
13 20:14:48 PDT 1996.

We have tested our case, and this bug seems not to be fixed in EBF6277
or in EBF6417

--

  \||/        Best regards,

 / (__,,,,|   Micro Design AS
/ _)          Trondheim, Norway

http://ourworld.compuserve.com/homepages/masterdat

 
 
 

@@identity crisis?

Post by RGCramot » Thu, 08 Aug 1996 04:00:00



writes:

Quote:>This looks like a bug we've been experiencing on version 11.01 on
>Solaris 2.4.  I'm told (but have not tested) that it is fixed in the next
>release (11.011).  Has anyone tested this version?

Yes, It failed with the same problem.

I'm running Sun Solaris 2.4 OS with 11.0.1.1 <-EBF 6277

Below are my results:
1> /*
2> create table dammit
3> (
4>       id     numeric(7) identity
5>      ,name   varchar(8)
6> )
7>
8> create table nonsense
9> (
10>       name   varchar(8)
11> )
12> */
13> insert nonsense values ("foo")
14> insert nonsense values ("bar")
15> go
(1 row affected)
(1 row affected)
1>  insert dammit values ("foo")
2> go
(1 row affected)

2> go

 -----------------------------------------
                                         1

(1 row affected)
1>  alter table nonsense add primary key (name)
2> go
1> alter table dammit add foreign key (name) references nonsense (name)
2> go
1>  insert dammit values ("bar")
2> go
(1 row affected)

2> go

 -----------------------------------------
                                         0

(1 row affected)
1> select * from dammit
2> go
 id         name
 ---------- --------
          1 foo
          2 bar

(2 rows affected)

2> go

 ------------------------------------------------------------------------
 SQL Server/11.0.1.1/P/Sun_svr4/OS 5.4/1/OPT/Wed May 29 03:23:32 PDT 1996

(1 row affected)

Richard Cramotte, Jr.
Sybase DBA

 
 
 

1. @@identity crises

I have a table with an integer identity field. After I execute an
CRecordset::AddNew() and Update() in VC++5, how can I retrieve the identity
value of the record I just added (without requerying and going back to look
for it)?


statement and retrieve the results into my C++ module.

2. how

3. Identity Crisis

4. fix for palloc() of user-supplied length

5. @@IDENTITY Crisis: VB6 + ADO2.1 + SS6.5

6. Linked Server Problem

7. Identity Crisis

8. distinct

9. Identity Crisis.

10. IDENTITY crisis.

11. Identity Crisis!

12. My SQL Server is Having an Identity Crisis

13. IDENTITY crisis....