Is executeQuery() locking the rows?
Hi,
Is executing the following statements lock the rows in database even if myView is a sql_only view? On the other words is executeQuery() locking the rows implicitly?
myView.setWhereClause(....where clause...);
myView.executeQuery();
please advice.Thanks.
Steven, That's good for me to hear this performance problem is not coming from the executeQuery() method. Let me explain more about this, maybe this is something in application module setting that I am not aware of that.
I have a jsp page, that gets view object name as a parameter. At the top of this page an application module and the view object instantiated using tags approach. Then the java code reads all the columns from the view using myView.getAttributeDefs() and
Shows the columns name along with a input box for each( like query page created by wizard). User could define the values in those input boxes. Then the code constructs the WHERE clause based on values entered by user ( and columns name came from the view definition) . at the end when user click on a button( named Find), the page sets the WHERE clause and executes the query and sets the view object based on user defined WHERE clause at runtime ( similar to query page created by wizard).
Problem:
Example1 : Pretend client1 clicks the Find button and the page is executing the executeQuery() method. If at this time client2 calls this page, the page loads fast but the columns shows after a delay. this delay is depend on how fast the executeQuery() is. ( this is my understanding, not sure).
Example2 : Pretend the query takes 2 seconds to be executed when only one client fires that using this page. But takes 10 seconds if two clients at the same time click on the Find button on that page at the same time(after they entered the values on input boxes). And that’s maybe more for three clients.
On the other words when the executeQuery() is executing for one client, the entire application locks( else where fires the executeQuery() ) for the other clients until the first one released. That’s why I guess ( just guess) this is maybe the behavior of the executeQuery(). Hope this guessing is not true. But what else could be. Is any parameter in application module that need to be altered? Or something on web server (9iAS)?
Please advice me, even if you are agree or disagree with my guess.
Thanks for your advice.
Similar Messages
-
ADF BC , lock the rows sometimes and do release it
Hi
thank you for reading my psot
i think ADF BC sometimes lock my Rows in table and does not allow other to change them , sometimes the lock goes too long time without any reason
(a record insert lock the rows until i restart the APPS) i should say that during record insert and commit may some exception occurs that prevent the ADFBC to commit the changes.
should it be like that ?
thanksAre you seeing this problem in the Business Components tester?
Can you reproduce in a simple case?
Is there a specific JBO error appearing?
Regards
Grant Ronald
Oracle Product Management -
How to lock the rows in program
how to lock the rows in program
Do not create a duplicate thread.
many had already answered your query here.
how to lock the rows in program
Regards,
Prazy -
How to lock the rows in a transaction so others cant modify the rows
Hi,
I want few suggestion in the following scenario .
I have a few records ( say 100 ) in a table which Im sending to the client over a network and are populated in a swing GUI...Now the client selects few of them ( say 3 ) and submits to the server. Now the server should assign a number to those rows and store them in the database. As it is a multi client environment While assigning the number it should check that no other client has already assigned a number to at lease to one of the row in the meantime. in that case it shoudl fail.
In this case i want to lock those 3 records when the request arrives at the server assign number commit and release the lock.
I want to avoid deadlocks.
Can any one suggest me whoch locking policy should i use and how ?
Thanx in advance...
MahiIt depends on how acceptable it is for your commit to fail. By far the easiest and safest thing to do is use Optimistic Locking. This way if the server tries to commit changes to something that has already been committed, an Optmistic Lock exception will be thrown. It's up to your application to handle this, and depending on your domain and the likelyhood of this happeneing, you could just tell the user "try again". The other option is pessemistic locking, which is very, very, dangerous (in my opinion). The main issue is that it's resource intensive, and different databases have different semantics on how it works.
IIWY, I'd look at Optimistic Locking in the docs and go from there.
- Don -
Lock the first row in an ordered table
Hi,
I have a table (TD_EVENTOS). I want to lock the row with te minimun value of a column (a timestamp called hora_evento) and some requirements of other columns. Then i build a cursor like this:
CURSOR c is select * from td_eventos where (...) order by hora_evento for update skip locked;
And then I make a fetch into this cursor and I get the row (locked) that I want. But i need the speedest way, and making that cursor it orders all rown in the table (when I only want the first row without lock) and when that table has 6000 or 7000 rows it wastes around 130 ms. My solution is to add to the WHERE a AND rownum < 50, and it only orders 50 rows (in 10 ms), but it orders 50 aleatory rows, and that`s not what I want.
Any solution faster?
Thanks!Sorry that wasn't clear of me and could be misleading. I didn't mean Oracle would have to do a full table scan, another access path such as an appropriate index scan would do. I was trying to get across that to do any kind of order or min or max, all records have to be investigated. Since the fact that you don't know a row is locked until you try to lock it, you clearly can't filter on it (it's not a data attribute).
Apologies for any confusion my earlier post might have caused.
The suggestion about using a sorted hash cluster still stands though, they are designed for FIFO queues.
Which reminds me - SKIP LOCKED is in fact undocumented but everybody knows that Oracle use it internally for doing AQ. Since it's undocumented, you don't know how it works, when it will work, when it won't and of course Oracle can turn around and say "we don't support this". -
Is it Necessary to lock the table while accessing the entries from table
Hi Gurus,
While optimization of the Program i came through one type of coding is in inside the Loop of The internal table which is processing BDC call transcation through updating the Custom table.
Before processing the BDC, the Custom table has been locked and read the entries from same custom table ,if the process fails then it waits for another 20 seconds and retrying the same for another time .I could not able to understand the Logic behind this.if it is not the Correct way then i can straight away remove this Part which is very well improve the perfromance of the Object.
For Your Better Understanding i have attached the Snippet of the Code .Please find the Code and advice me the same .
+LOOP AT i_stk_req INTO wa_stk_req.+
+** Lock is set to '0',meaning that no lock exist.+
++v_lock = 0. "FALSE.++
++* Preparing variable key for locking.++
++CLEAR v_key.++
++v_key = sy-mandt.++
++v_key+3(3) = wa_stk_req-lgnum.++
++v_key+6(4) = wa_stk_req-werks.++
++v_key+10(18) = wa_stk_req-matnr.++
++v_key+28(10) = wa_stk_req-charg.++
++* Try to lock the row for max of 100 times.++
++DO 10 TIMES.++
++* this perform sends sy-subrc EQ 1. in case of foreign lock.++
+PERFORM enqueue_tab IN PROGRAM saplsvix USING 'ZSDT_STK_REQ' v_key c_e c_e.+
+IF sy-subrc EQ 0. "If Enqueue is successful.+
+** set lock as TRUE+
++v_lock = 1. "TRUE++
++* selecting the latest entry for the table(Entry might have changed-refer to++
+SELECT SINGLE *+
++FROM zsdt_stk_req++
++INTO wa_stk_req++
++WHERE lgnum = wa_stk_req-lgnum++
++AND werks = wa_stk_req-werks++
++AND matnr = wa_stk_req-matnr++
++AND charg = wa_stk_req-charg.++
++IF sy-subrc NE 0. "Checking if select statement was successful++
++* Unlock the table row.++
++PERFORM enqueue_tab IN PROGRAM saplsvix USING c_table v_key c_e c_d.++
++v_lock = 0. "If unsuccessful.Then we set lock as FALSE.++
++EXIT.++
++ENDIF.++
++EXIT.++
++* If unsuccessful in locking then wait for 1 sec.++
+ELSE.+
+WAIT UP TO 20 SECONDS.+
+ENDIF.+
+** exit from DO. ENDDO.+
++ENDDO.++
++* v_lock will be FALSE if all attempts for lock was unsuccessful or++
++* if there is a problem in select single after lock.++
++IF v_lock = 0.++
++NEW-PAGE.++
++CLEAR v_display.++
++CONCATENATE text-004 text-012 wa_stk_req-matnr text-011 wa_stk_req-werks++
++text-019 wa_stk_req-lgnum text-020 wa_stk_req-charg INTO v_display SEPARATED BY space.++
++WRITE :/ v_display.++
++ENDIF.++
++* Only to process if lock is successful.++
++CHECK v_lock NE 0.++
++* If UPDATE IS FALSE that means that no updates need to be done.++
++* So we set v_update as FALSE in its initial state.++
++v_update = 0.++
++* Begin of Insert Optima App - 053++
++SELECT lgnum++
++lqnum++
++matnr++
++werks++
++charg++
++lgtyp++
++meins++
++verme++
++lgort++
++qplos++
++bestq++
++FROM lqua++
++INTO TABLE i_lqua1++
++WHERE lgnum EQ wa_lqua-lgnum++
++AND matnr EQ wa_lqua-matnr++
++AND werks EQ wa_lqua-werks++
++AND charg EQ wa_lqua-charg++
++AND bestq EQ wa_lqua-bestq++
++AND lgort EQ wa_lqua-lgort++
++AND verme GE 0.++
++* End of Insert Optima App - 053++
++* IF a requirement still exists.++
++IF wa_stk_req-verme > 0.++
++LOOP AT i_lqua INTO wa_lqua WHERE bestq = 'Q'++
++AND qplos NE 0++
++AND lgnum = wa_stk_req-lgnum++
++AND werks = wa_stk_req-werks++
++AND matnr = wa_stk_req-matnr++
++AND charg = wa_stk_req-charg.++
++CLEAR v_target.++
++CHECK wa_stk_req-lgtyp = wa_lqua-lgtyp OR wa_stk_req-lgtyp IS INITIAL.++
++* checking if still some stock needs to be transported.++
++IF wa_stk_req-verme < 0.++
++EXIT.++
++ENDIF.++
++* we need to send the entire lot if the stock belongs to quality inspection++
++IF wa_stk_req-verme >= wa_lqua-verme.++
++IF wa_stk_req-lgort IS INITIAL.++
++* fetch the Storage location value from the two custom tables.++
++PERFORM f_fetch_lgort.++
++ELSE.++
++v_lgort = wa_stk_req-lgort.++
++ENDIF.++
++* checking if v_lgort is not initial.++
++CHECK NOT v_lgort IS INITIAL.++
++* Calling QAC2++
++PERFORM f_qac2.++
++* Checking if Post Good was successful.++
+IF NOT wa_qamb-mblnr IS INITIAL.+
+REFRESH i_lqua1.+
+SELECT lgnum+
+lqnum+
+matnr+
+werks+
+charg+
+lgtyp+
+meins+
+verme+
+lgort+
+qplos+
+bestq+
+FROM lqua+
+INTO TABLE i_lqua1+
+WHERE lgnum EQ wa_lqua-lgnum+
+AND matnr EQ wa_lqua-matnr+
+AND werks EQ wa_lqua-werks+
+AND charg EQ wa_lqua-charg+
+AND bestq EQ wa_lqua-bestq+
+AND lgort EQ wa_lqua-lgort+
+AND verme GE 0.+
+SORT i_lqua1 BY lgtyp.+
+CLEAR: wa_lqua1,+
+v_position.+
+READ TABLE i_lqua1 INTO wa_lqua1 WITH KEY lgtyp = wa_lqua-lgtyp.+
+IF sy-subrc EQ 0.+
+v_position = sy-tabix.+
+ENDIF.+
+SELECT SINGLE lgnum+
+ubnum+
+FROM lubu+
+INTO wa_lubu+
+WHERE lgnum = wa_lqua-lgnum+
+AND mblnr = wa_qamb-mblnr.+
+CLEAR i_bdcdata.+
+REFRESH i_bdcdata.+
+REFRESH i_messtab.+
+CLEAR wa_bdcdata.+
+wa_bdcdata-program = 'SAPML03T' .+
+wa_bdcdata-dynpro = '0141' .+
+wa_bdcdata-dynbegin = 'X' .+
+APPEND wa_bdcdata TO i_bdcdata .+
+CLEAR wa_bdcdata .+
+wa_bdcdata-fnam = 'BDC_OKCODE' .+
+wa_bdcdata-fval = '/00' .+
+APPEND wa_bdcdata TO i_bdcdata .+
+CLEAR wa_bdcdata .+
+wa_bdcdata-fnam = 'LUBU-UBNUM'.+
+wa_bdcdata-fval = wa_lubu-ubnum.+
+APPEND wa_bdcdata TO i_bdcdata .+
+CLEAR wa_bdcdata .+
+wa_bdcdata-fnam = 'LUBU-LGNUM'.+
+wa_bdcdata-fval = wa_lqua-lgnum.+
+APPEND wa_bdcdata TO i_bdcdata .+
+CLEAR wa_bdcdata .+
+wa_bdcdata-fnam = 'RL03T-DUNKL'.+
+wa_bdcdata-fval = 'H'.+
+APPEND wa_bdcdata TO i_bdcdata .+
+CLEAR wa_bdcdata.+
+wa_bdcdata-program = 'SAPML03T' .+
+wa_bdcdata-dynpro = '0143' .+
+wa_bdcdata-dynbegin = 'X' .+
+APPEND wa_bdcdata TO i_bdcdata .+
+CONCATENATE 'RL03T-SELKZ('+
+v_position+
+')'+
+INTO v_str.+
+CLEAR wa_bdcdata .+
+wa_bdcdata-fnam = v_str.+
+wa_bdcdata-fval = 'X'.+
+APPEND wa_bdcdata TO i_bdcdata .+
+CLEAR wa_bdcdata .+
+wa_bdcdata-fnam = 'BDC_OKCODE' .+
+wa_bdcdata-fval = 'BU' .+
+APPEND wa_bdcdata TO i_bdcdata .+
+CLEAR wa_bdcdata.+
+wa_bdcdata-program = 'SAPML03T' .+
+wa_bdcdata-dynpro = '0142' .+
+wa_bdcdata-dynbegin = 'X' .+
+APPEND wa_bdcdata TO i_bdcdata .+
+CLEAR wa_bdcdata .+
+wa_bdcdata-fnam = 'BDC_OKCODE' .+
+wa_bdcdata-fval = 'BU' .+
+APPEND wa_bdcdata TO i_bdcdata .+
+*......changes as per ticket 44206+
++* CLEAR wa_bdcdata .++
++* wa_bdcdata-fnam = 'LQUAU-KZUAP(01)'.++
++* wa_bdcdata-fval = 'X'.++
++* APPEND wa_bdcdata TO i_bdcdata .++
+*......end of changes as per ticket 44206+
+CALL TRANSACTION 'LT05' USING i_bdcdata+
+OPTIONS FROM wa_ctu_params+
+MESSAGES INTO i_messtab.+
Regards,
Rajahi , please check the link below
[http://help.sap.com/saphelp_nw70/helpdata/en/41/7af4c5a79e11d1950f0000e82de14a/content.htm|http://help.sap.com/saphelp_nw70/helpdata/en/41/7af4c5a79e11d1950f0000e82de14a/content.htm] -
How to lock a row in a db2/400
Hi all,
Could someone show me how to lock a row in the database DB2/400
The scenario:
DB.beginTransaction
User 1 gets a row with a column bill_number
"select bill_number from numbers where pk = xxx for update"
aux_bill_number = bill_number
USER 1 updated this row
"update numbers set bill_number = bill_number +1 where pk = xxx "
USER 1, like final step, insert aux_bill_number in other table as primary key
DB.commitTransaction
While doing so,
User 2 also gets a row with a bill_number. this user must take bill_number with value 2, but take the same value 1
This it causes key duplicated in the destiny table.
Please, help me.
How I must lock the row not to allow to read until finishing the previous transaction?Hi all,
Could someone show me how to lock a row in the
database DB2/400Isn't SELECT FOR UPDATE standard?
>
The scenario:
DB.beginTransaction
er 1 gets a row with a column bill_number
"select bill_number from numbers where pk =
xxx for update"
aux_bill_number = bill_number
1 updated this row
"update numbers set bill_number = bill_number
+1 where pk = xxx "
USER 1, like final step, insert aux_bill_number in
other table as primary key
DB.commitTransactionSounds like you're trying to do something that a JOIN would do better.
While doing so,
User 2 also gets a row with a bill_number. this user
must take bill_number with value 2, but take the
same value 1
This it causes key duplicated in the destiny table.
Please, help me.
How I must lock the row not to allow to read until
finishing the previous transaction?Setting the isolation level to SERIALIZABLE might help.
% -
How to lock a row by using 'for update'?
how to lock a row by using 'for update'?
Hi,
SELECT * FROM <TABLE> WHERE <PK_COLUMN>=<VALUE> FOR UPDATE NOWAITThis will help in locking the row with the primary key value that you provide
cheers
VT -
Is there a way to BULK COLLECT with FOR UPDATE and not lock ALL the rows?
Currently, we fetch a cursor on a few million rows using BULK COLLECT.
In a FORALL loop, we update the rows.
What is happening now, is that we run this procedure at the same time, and there is another session running a MERGE statement on the same table, and a DEADLOCK is created between them.
I'd like to add to the cursor the FOR UPDATE clause, but from what i've read,
it seems that this will cause ALL the rows in the cursor to become locked.
This is a problem, as the other session is running MERGE statements on the table every few seconds, and I don't want it to fail with ORA-0054 (resource busy).
What I would like to know is if there is a way, that only the rows in the
current bulk will be locked, and all the other rows will be free for updates.
To reproduce this problem:
1. Create test table:
create table TEST_TAB
ID1 VARCHAR2(20),
ID2 VARCHAR2(30),
LAST_MODIFIED DATE
2. Add rows to test table:
insert into TEST_TAB (ID1, ID2, LAST_MODIFIED)
values ('416208000770698', '336015000385349', to_date('15-11-2009 07:14:56', 'dd-mm-yyyy hh24:mi:ss'));
insert into TEST_TAB (ID1, ID2, LAST_MODIFIED)
values ('208104922058401', '336015000385349', to_date('15-11-2009 07:11:15', 'dd-mm-yyyy hh24:mi:ss'));
insert into TEST_TAB (ID1, ID2, LAST_MODIFIED)
values ('208104000385349', '336015000385349', to_date('15-11-2009 07:15:13', 'dd-mm-yyyy hh24:mi:ss'));
3. Create test procedure:
CREATE OR REPLACE PROCEDURE TEST_PROC IS
TYPE id1_typ is table of TEST_TAB.ID1%TYPE;
TYPE id2_typ is table of TEST_TAB.ID2%TYPE;
id1_arr id1_typ;
id2_arr id2_typ;
CURSOR My_Crs IS
SELECT ID1, ID2
FROM TEST_TAB
WHERE ID2 = '336015000385349'
FOR UPDATE;
BEGIN
OPEN My_Crs;
LOOP
FETCH My_Crs bulk collect
INTO id1_arr, id2_arr LIMIT 1;
Forall i in 1 .. id1_arr.COUNT
UPDATE TEST_TAB
SET LAST_MODIFIED = SYSDATE
where ID2 = id2_arr(i)
and ID1 = id1_arr(i);
dbms_lock.sleep(15);
EXIT WHEN My_Crs%NOTFOUND;
END LOOP;
CLOSE My_Crs;
COMMIT;
EXCEPTION
WHEN OTHERS THEN
RAISE_APPLICATION_ERROR(-20000,
'Test Update ' || SQLCODE || ' ' || SQLERRM);
END TEST_PROC;
4. Create another procedure to check if table rows are locked:
create or replace procedure check_record_locked(p_id in TEST_TAB.ID1%type) is
cursor c is
select 'dummy'
from TEST_TAB
WHERE ID2 = '336015000385349'
and ID1 = p_id
for update nowait;
e_resource_busy exception;
pragma exception_init(e_resource_busy, -54);
begin
open c;
close c;
dbms_output.put_line('Record ' || to_char(p_id) || ' is not locked.');
rollback;
exception
when e_resource_busy then
dbms_output.put_line('Record ' || to_char(p_id) || ' is locked.');
end check_record_locked;
5. in one session, run the procedure TEST_PROC.
6. While it's running, in another session, run this block:
begin
check_record_locked('208104922058401');
check_record_locked('416208000770698');
check_record_locked('208104000385349');
end;
7. you will see that all records are identified as locked.
Is there a way that only 1 row will be locked, and the other 2 will be unlocked?
Thanks,
Yoni.I don't have database access on weekends (look at it as a template)
suppose you
create table help_iot
(bucket number,
id1 varchar2(20),
constraint help_iot_pk primary key (bucket,id1)
organization index;not very sure about the create table syntax above.
declare
maximal_bucket number := 10000; -- will update few hundred rows at a time if you must update few million rows
the_sysdate date := sysdate;
begin
truncate table help_iot;
insert into help_iot
select ntile(maximal_bucket) over (order by id1) bucket,id1
from test_tab
where id2 = '336015000385349';
for i in 1 .. maximal_bucket
loop
select id1,id2,last_modified
from test_tab
where id2 = '336015000385349'
and id1 in (select id1
from help_iot
where bucket = i
for update of last_modified;
update test_tab
set last_modified = the_sysdate
where id2 = '336015000385349'
and id1 in (select id1
from help_iot
where bucket = i
commit;
dbms_lock.sleep(15);
end loop;
end;Regards
Etbin
introduced the_sysdate if last_modified must be the same for all updated rows
Edited by: Etbin on 29.11.2009 16:48 -
How to find out, who locked the same row
Dears,
I have a problem,
sometimes our user complain that, when he tyring to make a transaction to a specific customer's Account
its says 'Some other user access the same account, keep trying...' (like this).
and in this response I just kill that user's session. then he can make the transaction by reconnecting.
sometimes my solution(killing the session) can not slove this problem.it stayed even 5/6 hours long.
in this time,i cannot find any bloking session or such a long waiting session.
In this Scenario..
I need to find out who(SID,SERIAL#,USERNAME) locked the same ROW (not table).
There are many users who are locking different rows of the same table at the
same time. I need to find the one who locked my row.
is it possible to find out, who locked the specific customer's Account ?
I am trying to find out by the following query but failed.
SELECT s.SID, serial#, machine, osuser, terminal, b.object_name,
row_wait_obj#, row_wait_file#, row_wait_block#, row_wait_row#,
DBMS_ROWID.rowid_create (1,
row_wait_obj#,
row_wait_file#,
row_wait_block#,
row_wait_row#
) rowidd
FROM v$session s, dba_objects b
WHERE s.row_wait_obj# = b.object_id
SELECT *
FROM (SELECT s.SID, serial#, machine, osuser, terminal, b.object_name,
row_wait_obj#, row_wait_file#, row_wait_block#, row_wait_row#,
DBMS_ROWID.rowid_create (1,
row_wait_obj#,
row_wait_file#,
row_wait_block#,
row_wait_row#
) rowidd
FROM v$session s, dba_objects b
WHERE s.row_wait_obj# = b.object_id)
WHERE rowidd IN (SELECT ROWID
FROM account_mas
WHERE branch = '999' AND accout_no = '009990215454')
please help me...
My Database version- 10.2.0.4, windows
Regards
Halim
Edited by: Abdul Halim on Oct 26, 2009 2:43 AMJust check with this query, find the lock and kill the session.
select b.session_id ,a.SERIAL#, a.username "Blocker Details"
from v$session a,dba_lock b
where b.session_id = a.sid
and b.blocking_others = 'Blocking';
Regards
Asif kabir -
I realize that this is probably a simple question and
solution but I need to lock the category row on a cfquery table so
that the categories for each itme remain at the top of the screen
and doesn't scroll out of view. Below is some code (as attached) as
an example. Thanks in advance, Tripp.quote:
Originally posted by:
fbradd
I realize that this is probably a simple question and
solution but I need to lock the category row on a cfquery table so
that the categories for each itme remain at the top of the screen
and doesn't scroll out of view. Below is some code (as attached) as
an example. Thanks in advance, Tripp.
Either use cfgrid or put your data rows in a frame or iframe. -
How do I lock the numbers on a French keyboard if I'm using a small blue tooth keyboard with no number pad?
How do I lock the numbers on a French keyboard if I'm using a small blue tooth keyboard with no number pad?
-
Can the row ID number be locked when moving task around in the schedule?
I have a schedule in which I want to move row ID 9 to row ID 5; but do NOT want the row ID of 9 to change to 5. I want to keep original row ID's upon moving them around in my schedule. Is this possible? If yes, how?
Thank youAre you trying to do this with a BizTalk app? 2000/2002?
-
To lock the output of a SELECT query
Hi,
I want to lock the output of a SELECT query to some transaction.
I have wriiten it as follows , the output of the query is a single row;
SELECT empname
FROM employees
where empid = 100
FOR UPDATE;
Specifying only FOR UPDATE is proper or do i need to specify some more clause ??
Thanks.bscalzo wrote:
You can also specify the columns to lock if you like:
select x, y, z from aaa where x = 1 for update of x, y;
But the locking is still currently only done at the row level - but who knows what the future might offer. May not hurt to have the columns named for thay day when the syntax and engine sync up :)It might be worth to amend that specifying the columns is already particularly relevant if you select from multiple tables/views in order to specify which rows of which table/view to lock.
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/ -
HOW TO DELETE THE ROW FROM DATABASE
hI,
Iam pasting my code below.My problem isi retrieve rows from database and display them in jsp page in rows.For each row there is delete hyperlink.Now when i click that link i should only delete the row corresponding to that delete link temporarily but it should not delete the row from database now.It should only delete the row from database when i click the save button.How can i do this can any one give some code.
thanks
naveen
[email protected]
<%@ page language="java" import="Utils.*,java.sql.*,SQLCon.ConnectionPool,java.util.Vector,java.util.StringTokenizer" %>
<html>
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Item Details</title>
<script>
function submitPage()
document.details.action = "itemdetails.jsp" ;
document.details.submit();
</script>
</head>
<body>
<form name="details" action="itemdetails.jsp" method="post">
<%
ConnectionPool pool;
Connection con = null;
Statement st;
ResultSet rs =null;
%>
<table border="0" cellpadding="0" cellspacing="0" width="328">
<tr>
<td width="323" colspan="4"><b>Reference No :</b> <input type="text" name="txt_refno" size="14">
<input type="submit" value="search" name="search" ></td>
</tr>
<tr>
<td width="81" bgcolor="#000099"><font color="#FFFFFF"><b>Item Code</b></font></td>
<td width="81" bgcolor="#000099"><font color="#FFFFFF"><b>Item No</b></font></td>
<td width="81" bgcolor="#000099"><font color="#FFFFFF"><b>Amount </b></font></td>
<td width="80" bgcolor="#000099"> </td>
</tr>
<%
pool= new ConnectionPool();
Utils utils = new Utils();
double total =0.00;
String search =utils.returnString(request.getParameter("search"));
if(search.equals("search"))
try
String ref_no =utils.returnString(request.getParameter("txt_refno"));
String strSQL="select * from ref_table where refno='" + ref_no + "' ";
con = pool.getConnection();
st=con.createStatement();
rs = st.executeQuery(strSQL);
while(rs.next())
String itemcode=rs.getString(2);
int item_no=rs.getInt(3);
double amount= rs.getDouble(4);
total= total + amount;
%>
<tr>
<td width="81"><input type=hidden name=hitem value=<%=itemcode%>><%=itemcode%></td>
<td width="81"><input type=hidden name=hitemno value=<%=item_no%>><%=item_no%></td>
<td width="81"><input type=hidden name=hamount value=<%=amount%>><%=amount%></td>
<td width="80"><a href="delete</td>
</tr>
<%
}catch(Exception e){}
finally {
if (con != null) pool.returnConnection(con);
%>
<tr>
<td width="323" colspan="4">
<p align="right"><b>Total:</b><input type="text" name="txt_total" size="10" value="<%=total%>"></td>
</tr>
<tr>
<td width="323" colspan="4">
<input type="button" value="save" name="save"></td>
</tr>
</table>
</form>
</body>
</html>You mean when you click on the hyperlink you want that row to disappear from the page, but not delete the row from the database until a commit/submit button is pressed?
Personally, I think I'd prefer that you have a delete checkbox next to every row and NOT remove them from the display if I was a user. You give your users a chance to change their mind about their choice, and when they're done they can see exactly which rows will be deleted before they commit.
You know your problem, of course, so you might have a good reason for designing it this way. But I'd prefer not removing them from the display. JMO - MOD
Maybe you are looking for
-
Tips for printing photos with HP ePrint
Hello, I will be giving you guys a couple of tips on how to print photos with HP ePrint. These are general tips to make it a little more easier to use HP ePrint. #1: Have 4" x 6" photo paper preloaded in your printer The first step in getting qual
-
I used to have the color picker tab in the toolbar on the right (above the adjustments and layers tabs, now I have a different color selection tool that has a color strip, with the RGB sliders above it. I want to reset it to the color picker that had
-
Date validation in the selection screen
Hi I am new to all this..so pls help me with this... I need to validate my input field in the selection screen to have the format as YYYYMMDD i.e user is allowed to enter the date in this format only!! Now how to validate this kind of a format??
-
Screwed up the initial start-up with Migration assistant
I just recieved my 27" refub iMac, and was all excited to transfer my files over from my old iMac. When I started the system up, I followed all the directions, followed the migration assistant, and everything sync'd. Great. Until... Not only did all
-
I know everyone has answered this a thousand times and that theres updates and everything for it. But i just got my new 160 gb classic and im running windows vista and everything is fully up to date but my iPod still gets corrupted when i sync it to