Solved

oracle table handlers

Posted on 2004-09-03
3
613 Views
Last Modified: 2010-08-05
This is regarding the custom form which i'll be registering in apps

I have created a form and the base table is a view.
The table is having around 70 columns and i have created view with rowid and all the columns from the base table.

 i'll be displaying only 13 columns in the screen and updating only one column
out of 13 columns some are not null columns and some accept null values alos
I have written two table handlers on the block, on-update and on-lock

my question is how do i need to frame the on-lock procedure logic....
do i need to include all the 70 columns in the lock-row logic
or do i need to check for the 13 columns which are displayed on the screen
or is it enough if i check for the non-null colums in the lock-row procedure..

FYI : i'm following the same steps as mentioned in the oracle applications developer guides ..
topic : Example Client–Side Table Handler  page 4-21
0
Comment
Question by:hiswapna
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 15

Accepted Solution

by:
andrewst earned 125 total points
ID: 11971979
Interesting question.  My initial thought is that you only need to check the 13 columns, because the user is unconcerned with the other 57.  Here's my reasoning:

Suppose you check them all, and find that someone else has changed col66, which your form doesn't use.  The error is raised telling the user the he/she needs to requery the record as it has been changed.  The user requeries the record, which comes back looking exactly the same as before, and then successfully locks it.  So nothing has been gained by the initial lock failure.
0

Featured Post

SharePoint Admin?

Enable Your Employees To Focus On The Core With Intuitive Onscreen Guidance That is With You At The Moment of Need.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Truncate is a DDL Command where as Delete is a DML Command. Both will delete data from table, but what is the difference between these below statements truncate table <table_name> ?? delete from <table_name> ?? The first command cannot be …
From implementing a password expiration date, to datatype conversions and file export options, these are some useful settings I've found in Jasper Server.
This video explains at a high level about the four available data types in Oracle and how dates can be manipulated by the user to get data into and out of the database.
This video shows syntax for various backup options while discussing how the different basic backup types work.  It explains how to take full backups, incremental level 0 backups, incremental level 1 backups in both differential and cumulative mode a…
Suggested Courses

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question