Re: What's special about this create table statement?

On 4 Jan 2006 14:53:46 -0800, "dean" <deanbrown3d_at_yahoo.com> wrote:

>CREATE TABLE "UPD"."SELECTED_NODES" ("SEQ_I" NUMBER NOT NULL,
> "NODE_I" NUMBER NOT NULL, "LABEL_S" VARCHAR2(1 byte),
> CONSTRAINT "PK_SELECTED_NODES" PRIMARY KEY("NODE_I")
> USING INDEX
> STORAGE ( INITIAL 0K NEXT 0K MINEXTENTS 0 MAXEXTENTS 0
> PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1) PCTFREE 10
> INITRANS 2 MAXTRANS 255) PCTFREE 10 PCTUSED 40 INITRANS 1
> MAXTRANS 255
> STORAGE ( INITIAL 0K NEXT 0K MINEXTENTS 0 MAXEXTENTS 0
> PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1)
> NOLOGGING
>
>I'm trying to determine what it is about this table that lets me insert
>records into it in one session, commit them, and still not see them in
>another identical (SQL+) session.
>
>It was set up so that different users can insert and delete
>independently and for it to look like their data is the only data in
>the table, I just don't see how it works.

 That's an ordinary heap table and so cannot exhibit that behaviour.

 A global temporary table would fit the requirement, but that's not what's created by the DDL above.

-- 
Andy Hassall :: andy@andyh.co.uk :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool