NULL PRIMARY
>>>>>>> KEY
>>>>>>> GENERATED ALWAYS AS IDENTITY (START WITH 1, INCREMENT BY 1) ,
>>>>>>> monday VARCHAR(16),
>>>>>>> tuesday VARCHAR(16), wednesd
e that you're doing a sequential table scan.
HTH
-Mike
_____
From: jay _ [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2008 4:16 AM
To: derby-user@db.apache.org
Subject: memory usage for row delete cascade
Hi all,
I have a database with three tables (Table_
cascade).
>>>>>
>>>>> I am guessing child_id does not need a separate index to be generated
>>>>> because it is the primary key in Child_info table and atttendance_info
>>>>> tables. However child_id cant be either unique or primary in
&g
able scan.
HTH
-Mike
_
From: jay _ [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2008 4:16 AM
To: derby-user@db.apache.org
Subject: memory usage for row delete cascade
Hi all,
I have a database with three tables (Table_A, Table_B and Table_C).
There
is
one identity
; My query times for something like
>>>
>>> DELETE FROM CHILD_INFO WHERE CHILD_ID = 1
>>>
>>> is around 6 seconds with only two row entries CHILD_INFO, 6 row entries
>>> in
>>> PARENT_INFO and just one entry in ATTENDANCE_INFO!
>>>
&
at you're doing a sequential table scan.
HTH
-Mike
_
From: jay _ [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2008 4:16 AM
To: derby-user@db.apache.org
Subject: memory usage for row delete cascade
Hi all,
I have a database with three tables (Table_A, Ta
index on Col_x_ID? Is Col_x_ID a unique ID? If
> so, is this the primary key for the table?
>
>
>
> That would be the first thing to look at. If no index exists, my guess
> would
> be that you're doing a sequential table scan.
>
>
>
> HTH
>
>
>
> -
the first thing to look at. If no index exists, my guess would
be that you're doing a sequential table scan.
HTH
-Mike
_
From: jay _ [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2008 4:16 AM
To: derby-user@db.apache.org
Subject: memory usage for row delete cas
Hi all,
I have a database with three tables (Table_A, Table_B and Table_C). There is
one identity column in Table_A which acts as a foreign key in Tables B and C
with an ON DELETE CASCADE.
Here is the table structure
Table A : Col_x_ID , Coly_Name,
Table B : Col_p_ID, Col_q_Name,
