Avoid duplicates in the query
Hello..I wrote the following to meet the requirement... query but duplicates
SELECT a.rpper, a.idate, a.icycle, b.rpper,
b.idate, b.icycle
FROM i_sum a, i_sum b
WHERE a.rc = b.py
AND a.py = b.rc
AND a.prd = b.prd
AND a.svc = b.svc
AND a.itype = 'bieral'
AND b.itype = 'bieral'
AND a.dir = '-'
AND b.dir = '-'
AND ( (a.idate != b.idate)
OR (a.icycle != b.iycle)
)
ORDER BY a.rpper, b.rpperA-G-11/9-SMS 30-Nov-09 112 G-A-11/9-SMS 31-Aug-09 113
--------
------
G-A-11/9-SMS 31-Aug-09 113 A-G-11/9-SMS 30-Nov-09 112
-----
-----How can I avoid these data
Thank you...
Smile says:
"I should meet on condition that a.icycle!" = b.icycle
So I can't say the condition where a.icycle > b.icycle
Yes you can. Think of it like this, suppose you have a list of numbers, 1, 2 and 3.
You want to join this list of numbers to himself, ending up with pairs of numbers, but you don't want the same number appearing twice in any pair, nor do you want to reverse pairs that occur.
That is to say. (1, 1), (2, 2) etc are not valid. (this is the equivalent you are a.icycle! = b.icycle). In addition, (1.2) and (2, 1) are not valid.
Then, join the list to itself based on the num1! = num2 condition only will give you:
1, 2
1, 3
2, 1
2, 3,
3, 1
3, 2
You can see that you have pairs reversed now appearing - IE. (1,2) and (2,1), (1, 3) and (3, 1) who - did I mention? -We do not want.
to prevent that from happening, you must stop to join the list with numbers earlier than the number that you join with. That is to say.
1, 2
1, 3
2 .....<----- can't="" join="" with="" 1,="" as="" 1="" is="" less="" than="" 2,="" and="" we="" already="" have="" (1,2)="" in="" the="" list.="" nor="" can="" you="" join="" with="" 2,="" as="" 2="2" and="" we="" are="" excluding="" them.="" therefore="" we="" start="" joining="" with="" 3="" -="" ie.="" 2=""><>
Thus, the new list becomes:
1, 2
1, 3
2, 3
This is the equivalent of the join with a.icycle<>
ETA: Perhaps a slightly more graphic response would help:
{code}
with the line = col under the join:
1 2 3 4
1 x x x x
2 x x x x
3 x x x x
4 x x x x
with line! = col under the join:
1 2 3 4
1 x x x
2 x x x
3 x x x
4 x x x
with the line< col="" as="" the="">
1 2 3 4
1 x x x
2 x
x 3
4
{code}
Published by: Boneist on January 18, 2011 14:07
Tags: Database
Similar Questions
-
Avoid duplicates when you import XMLs?
There are a few versions, we have fixed the problem to get the duplicate items when you import new projects in another. This was very helpful.
However, I have noticed that when you import XMLs, first does not apply the same level of... discretion
Is it possible to get XMLs for import without creating duplicate items? I found a workaround by first import the XML file into a new project and then import this project first to my main project... but when I'm in a great documentary film which takes 3-4 minutes to open each time, it's not ideal.
This is particularly important for people using the Pluraleyes because organize us images in first and then export to the EP, and then must bring with XMLs, and it would be great if we didn't have to do a bunch of media management manual to avoid duplicates in the project file.
Thank you!R
Hi Ryan,
Get your feature to the appropriate string request by filling out this form: http://adobe.ly/feature_request
Thank you
Kevin
-
How to import images in the latest Lightroom who don't not take FOREVER and avoid duplicates?
I have the error and installed the "update" (highly questionable terms of ). Now, import takes FOREVER and I don't see the option to avoid duplicates?
Any help much appreciated.
I don't see the option to avoid duplication?
Adobe removed this feature (and many others) of the new import in CC 2015.2 / 6.2. They have apologized for that and for having introduced a large number of bugs, and in the next version they will be restoring the old import feature: Lightroom 6.2 version update and apologies, 6.2 Lightroom import update.
Meanwhile, while you could try to solve the problems with 2015.2.1 / 6.2.1 I recommend return you to 2015.1.1 / 6.1.1 the last stable release: http://www.lightroomqueen.com/how-do-i-roll-back-to-lightroom-2015-1-1-or-lightroom-6-1-1/. Many people who have done so, and the same Adobe now recommends if you have serious problems (and you'll very probably).
-
Get duplicates in the case and Count clause in the generation of reports
Hi all
Let me explain first Base (just the Section that is in the scope of the present code) then evil go to code and my problem.i have a Set of pre-defined tasks in * 'TASK' * Table.i have a system that puts the user's request by assigning the task to their request to Request.Each will be mapped to the Instance of the task (predefined) , it will remain in a separate table * "TASK_INSTANCE" * against the user of the application id. Each task has a predefined duration.and, that their maturity date is stored in the Time Stamp data type column.
My scenario is I need to generate report based the date.report requirement is complete, I need get the number of tasks that have the date of completion as today, tomorrow and the next day they grouped based on task names.
My problem is, im getting duplicates if I used separate. It is not possible to duplicate using the join because im using Group by task nameevery record in the Task_instance table has direct relationship with the task ID. For example: im getting a line with the County satisfying the Condition and the next row with empty set.i he cannot understand why happening.need your help to understand this.
Let me add the query below,
SELECT task.task_name,
* (CASE *)
WHEN ((TRUNC (SYSDATE) - TRUNC (task_instance.ptd_pdd_date)) =
(- 1).
THEN
* (COUNT (task_instance.ptd_pdd_date)) *.
END)
AS "1_day_behind."
* (CASE *)
WHEN ((TRUNC (SYSDATE) - TRUNC (task_instance.ptd_pdd_date)) =
(- 2).
THEN
COUNT (task_instance.ptd_pdd_date)
END)
AS "2_day_behind."
* (CASE *)
WHEN ((TRUNC (SYSDATE) - TRUNC (task_instance.ptd_pdd_date)) =
(- 3).
THEN
COUNT (task_instance.ptd_pdd_date)
END)
AS "3_day_behind".
The TASK task_instance
WHERE task.task_id = task_instance.task_id
AND task_instance.status_id = 1
AND task_instance.ptd_pdd_date IS NOT NULL
GROUP BY (TRUNC (SYSDATE) - TRUNC (task_instance.ptd_pdd_date)),
Task.Task_Name;
task_instance.status_id = 1 refers to the task located in "in progress".
It's overall results (example) I get. In this area, the UI_Contact_Customer task is repeated three times. features of different in separate lines and null in the line separate .i need to avoid these duplicates.please Advisor.
__________________________________________________________________________________
TASKNAME | "1_DAY_BEHIND" | "2_DAY_BEHIND" | "3_DAY_BEHIND" |
______________________________|________________|_________________|_________________|
UI_Conduct_Fiber_Plant_Survey___ | ___ | ___ | ___ |
UI_Conduct_Site_Survey___ | ___ | ___ | ___ |
UI_ConductFiberSurvey_C___ | ___ | ___ | ___ |
UI_ConductSiteSurvey_C _ | ___ | ___ | ___ |
UI_Contact_Customer_____________|________________|_________________|_________________|
_ UI_Contact_Customer | ___10___ | ___ | ___ |
UI_Contact_Customer___ | ___ | ___ 12___ | ___ |
UI_Create_Account_Equip_C___ | ___ | ___ | ___ |
UI_Create_Account_Equipment___ | ___ | ___ | ___ |
UI_Create_CM_Ticket | | | |
______________________________|________________|_________________|_________________|
In the above result set, in particular UI_Contact_Customer task, ten of their instance with completion date tomorrow and 12 instance having the next day as the date of completion. I need to get all those as single line without duplicate.
Thank you
Jeevanand.KJeevanand K wrote:
I need to generate the report for the following scenarios
So what's the problem:
SELECT task.task_name, COUNT( CASE WHEN TRUNC(SYSDATE) - TRUNC(task_instance.ptd_pdd_date) = -1 THEN 1 END ) AS "1_day_ago", COUNT( CASE WHEN TRUNC(SYSDATE) - TRUNC(task_instance.ptd_pdd_date) = -2 THEN 1 END ) AS "2_day_ago", COUNT( CASE WHEN TRUNC(SYSDATE) - TRUNC(task_instance.ptd_pdd_date) = -3 THEN 1 END ) AS "3_day_ago", COUNT( CASE WHEN TRUNC(SYSDATE) - TRUNC(task_instance.ptd_pdd_date) = -14 THEN 1 END ) AS "2_weeks_ago", COUNT( CASE WHEN TRUNC(SYSDATE) - TRUNC(task_instance.ptd_pdd_date) < -3 THEN 1 END ) AS "more_than_4_days_ago" FROM task, task_instance WHERE task.task_id = task_instance.task_id AND task_instance.status_id = 1 GROUP BY task.task_name;Keep in mind "more_than_4_days_ago" includes tasks as filled with "2_weeks_ago".
SY.
-
How can I avoid duplicate emails in my Inbox O.E.?
duplicate emails
How can I avoid duplicate emails in my Inbox O.E.. I also receive emails in BT Yahoo Mail but only one every time. Thank you. Brian
Check out these links. I don't know if they are up to date, but it should get you going in the right direction. -
How to avoid synchronization of the settings between two computers
I have two computers (a desktop computer all-in-one DELL and HP laptop). Log-in at once is my Microsoft account.
PROBLEM: When I 'customize' screen on one, the same changes are made on the other. It is not desirable. How to avoid that, far from making a second Microsoft account?
To clarify - the ICONS are not duplicated, just any changes made to the themes of office such as colors or backgrounds.
Thanks in advance!
Hello Beckinista,
Thanks for posting your question on the Microsoft community.
Thank you for your query details.
I also like the fact you want to avoid synchronization of the settings between two computers.
I suggest you stop the synchronization of all of the settings between two computers and check if it helps.
Please see this link:
Sync between multiple PCs with OneDrive settings
http://Windows.Microsoft.com/en-us/Windows-8/sync-settings-PCsNote: Please see section "to stop all sync settings" in the article above.
I hope this information helps.
Please let us know if you need more help.
Thank you
-
Coordination of detail during the query mode
Forms 11g
I have a relationship of the master / detail, details of autoquery. the two blocks are displayed several records. I want to show a flag value (and the color attribute) next to the master if he got to the detail records.
To do this, I coded it in the post of the block in detail, because I wanted to avoid the questioning of the secondary table twice (one in the master post-requete and secondly in the population of retail block).
When running I run the query for the master, but the detail does not seem to be queried for all the record questioned captain. My tracking after request works only for the selected record of the master.
Is this normal? Is coordination suspended unless you are in NORMAL mode?
Yes, it comes to the features of normal forms. To highlight each master record based on if are detail records, you must query the table Details in the trigger of the Master post-requete.
You could simplify this by creating a database function that returns a TRUE/FALSE value rather than to perform a COUNT (*) SELECT your trigger after request. Then your trigger after query is simply:
BEGIN If ( YOUR_DB_FUNCTION = TRUE ) THEN Set_Item_Instance_Propety('YOUR_BLOCK',CURRENT_RECORD,PROPERTY,PROPERTY_VALUE); END IF; END;Craig...
-
Is it possible to ignore the duplicate in the ATG request?
If a user clicks twice or more than that of a button who invoke a formhandler submit action. Is there a way we can ignore duplicate of the user click applications?
Hi Jitendra,
To prevent duplicate on the sending of a form applications, you can use the RepeatingRequestMonitor, which is a very simple on the ATG box component, but quite effective.
To use this component, you must create an object of names like RepeatingRequestMonitor and he's a poseur of getter in your form Manager.
The syntax is as below: -.
If (RepeatingRequestMonitor.isUniqueRequestEntry ("YourFormHandler.handleSubmit")) {}
try {}
proceed with the execution of the method feature
}
{Finally
When the functionality of performance, remove this entry of the application
RepeatingRequestMonitor.removeRequestEntry ("YourFormHandler.handleSubmit");
}
} else {}
cause, perhaps create DropletFormException and return
}
Let me know for any query.
Kind regards
Prateek Gupta
-
How does whitespace or null values or characters set effect set in the query?
Hi all
I have a question about client side Oracle database tools. I have Oracle 11g installed on the server and I use PL/SQL developer tool to retrieve information from the server and then I copy paste this query in PL SQL Developer my company built in box of function of the application that executes the same query as client tools and the results.
When I write the request by spaces of the Tools client-side IE the PL/SQL developer tool and copy paste at my request of builtin company gives slow down me execution, but if I remove the white of the query space by copying the application of PL/SQL developer(client side tool) to Notepad first and then copy back at my request and gives me a faster execution.
For example:
Original Request: with whitespace
Select
*
Of
Double
Ask without spaces faster tracks:
Select * twice;
I want to the reason behind this slow execution and also if you could explain in detail would be great that I am no expert oracle.
Also, I wanted to know that character set parameters from the client side tools slow running query? As I copy the request of PL/SQL developer tool
Thank you
HP
HP, I have has been suggest you determine if the difference in performance is due to how the application prepares and processes SQL or if the difference is in Oracle. If you can duplicate the issue in Oracle using SQLPLus then you can use the Oracle tools such as autotrace, SQL, trace etc... to determine how Oracle handles each request. On the other hand if the time of execution in SQLPLus is the same then you know that the problem lies in the application. Depending on whether you have access to the source you can or will not be able to track down the issue and resolve it. Otherwise always paste the capture into the plan text and edit it to remove the unnecessary lines before copying them the text into your application tool.
- -
HTH - Mark D Powell.
-
steps to optimize the query on explain plan
Hello
Please find the described explain the plan of a query, and suggest me where and how can grant us the request.
{code}
-----------------------------------------------------------------------------------------------------------------------
| ID | Operation | Name | Lines | Bytes | TempSpc | Cost (% CPU). Time |
-----------------------------------------------------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 352K | 60 M | | 17677 (12) | 00:03:33 |
| 1. TRANSFORMATION OF THE TEMPORARY TABLE. | | | | | |
| 2. LOAD SELECT ACE | SYS_TEMP_0FD9FCB72_F58FAD20 | | | | | |
| 3. VIEW | | 22G | 3684G | | 96 M (100) | 320:57:19 |
| 4. UNIQUE FATE | | 22G | 4837G | 436G | 96 M (1) | 320:57:19 |
| 5. CONCATENATION. | | | | | |
|* 6 | HASH JOIN | | 1792M | 392G | | 52682 (26) | 00:10:33 |
| 7. VIEW | STAG_MASTER_VW | 39985 | 468K | | 2229 (1) | 00:00:27 |
|* 8 | MAT_VIEW FULL ACCESS | STAG_MASTER_MV | 39985 | 468K | | 2229 (1) | 00:00:27 |
|* 9 | HASH JOIN | | 1792M | 372G | 9320K | 43943 (16) | 00:08:48 |
| 10. VIEW | STAG_MANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| 11. MAT_VIEW FULL ACCESS | STAG_AANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| * 12 | EXTERNAL RIGHT HASH JOIN | | 676K | 128 M | 19 M | 29255 (1) | 00:05:52 |
| 13. VIEW | ABC_CDE_INDEX_CHG_VW | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 14 | TABLE ACCESS FULL | ABC_CDE_INDEX_CHG | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 15 | HASH JOIN | | 195K | 34 M | 9240K | 24001 (1) | 00:04:49 |
| 16. VIEW | STAG_NAMADDS_VW | 248K | 6316K | | 872 (1) | 00:00:11 |
| 17. MAT_VIEW FULL ACCESS | STAG_NAMADDS_MV | 248K | 6316K | | 872 (1) | 00:00:11 |
| * 18. OUTER HASH JOIN | | 114K | 17 M | 12 M | 21748 (1) | 00:04:21 |
| * 19. MAT_VIEW FULL ACCESS | STAG_ANAME_MV | 113K | 10 M | | 1085 (2) | 00:00:14 |
| 20. VIEW | ABC_CDE_INDEX_AST_VW | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 21. TABLE ACCESS FULL | ABC_CDE_INDEX_AST | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 22. HASH JOIN | | 89 M | 19G | | 46498 (16) | 00:09:18 |
| 23. VIEW | STAG_MASTER_VW | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 24. MAT_VIEW FULL ACCESS | STAG_MASTER_MV | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 25. HASH JOIN | | 89 M | 18G | 9320K | 43943 (16) | 00:08:48 |
| 26. VIEW | STAG_MANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| 27. MAT_VIEW FULL ACCESS | STAG_AANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| * 28. EXTERNAL RIGHT HASH JOIN | | 676K | 128 M | 19 M | 29255 (1) | 00:05:52 |
| 29. VIEW | ABC_CDE_INDEX_CHG_VW | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 30 | TABLE ACCESS FULL | ABC_CDE_INDEX_CHG | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 31. HASH JOIN | | 195K | 34 M | 9240K | 24001 (1) | 00:04:49 |
| 32. VIEW | STAG_NAMADDS_VW | 248K | 6316K | | 872 (1) | 00:00:11 |
| 33. MAT_VIEW FULL ACCESS | STAG_NAMADDS_MV | 248K | 6316K | | 872 (1) | 00:00:11 |
| * 34 | OUTER HASH JOIN | | 114K | 17 M | 12 M | 21748 (1) | 00:04:21 |
| * 35 | MAT_VIEW FULL ACCESS | STAG_ANAME_MV | 113K | 10 M | | 1085 (2) | 00:00:14 |
| 36. VIEW | ABC_CDE_INDEX_AST_VW | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 37 | TABLE ACCESS FULL | ABC_CDE_INDEX_AST | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 38 | HASH JOIN | | 4480K | 1004M | | 46189 (15) | 00:09:15 |
| 39. VIEW | STAG_MASTER_VW | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 40 | MAT_VIEW FULL ACCESS | STAG_MASTER_MV | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 41. HASH JOIN | | 4480K | 952 M | 9320K | 43943 (16) | 00:08:48 |
| 42. VIEW | STAG_MANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| 43. MAT_VIEW FULL ACCESS | STAG_AANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| * 44 | EXTERNAL RIGHT HASH JOIN | | 676K | 128 M | 19 M | 29255 (1) | 00:05:52 |
| 45. VIEW | ABC_CDE_INDEX_CHG_VW | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 46 | TABLE ACCESS FULL | ABC_CDE_INDEX_CHG | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 47 | HASH JOIN | | 195K | 34 M | 9240K | 24001 (1) | 00:04:49 |
| 48. VIEW | STAG_NAMADDS_VW | 248K | 6316K | | 872 (1) | 00:00:11 |
| 49. MAT_VIEW FULL ACCESS | STAG_NAMADDS_MV | 248K | 6316K | | 872 (1) | 00:00:11 |
| * 50 | OUTER HASH JOIN | | 114K | 17 M | 12 M | 21748 (1) | 00:04:21 |
| * 51 | MAT_VIEW FULL ACCESS | STAG_ANAME_MV | 113K | 10 M | | 1085 (2) | 00:00:14 |
| 52. VIEW | ABC_CDE_INDEX_AST_VW | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 53 | TABLE ACCESS FULL | ABC_CDE_INDEX_AST | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 54 | OUTER HASH JOIN | | 224KO | 50 M | 14 M | 32597 (4) | 00:06:32 |
| * 55 | HASH JOIN | | 64775 | 13 M | 7696K | 28458 (5) | 00:05:42 |
| * 56 | OUTER HASH JOIN | | 37855. 7245K | 5416K | 26763 (5) | 00:05:22 |
| * 57 | HASH JOIN | | 37675 | 4966K | | 6436 (18) | 00:01:18 |
| 58. VIEW | STAG_MASTER_VW | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 59 | MAT_VIEW FULL ACCESS | STAG_MASTER_MV | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 60 | HASH JOIN | | 37675 | 4525K | 9320K | 4206 (27) | 00:00:51 |
| 61. VIEW | STAG_MANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| 62. MAT_VIEW FULL ACCESS | STAG_AANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| * 63. MAT_VIEW FULL ACCESS | STAG_ANAME_MV | 113K | 10 M | | 1085 (2) | 00:00:14 |
| 64. VIEW | ABC_CDE_INDEX_AST_VW | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 65 | TABLE ACCESS FULL | ABC_CDE_INDEX_AST | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| 66. VIEW | STAG_NAMADDS_VW | 248K | 6316K | | 872 (1) | 00:00:11 |
| 67. MAT_VIEW FULL ACCESS | STAG_NAMADDS_MV | 248K | 6316K | | 872 (1) | 00:00:11 |
| 68. VIEW | ABC_CDE_INDEX_CHG_VW | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 69 | TABLE ACCESS FULL | ABC_CDE_INDEX_CHG | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 70 | OUTER HASH JOIN | | 11201 | 2570K | | 23267 (6) | 00:04:40 |
| * 71 | HASH JOIN | | 3239 | 702K | | 20816 (6) | 00:04:10 |
| * 72 | OUTER HASH JOIN | | 1893 | 362K | | 19942 (7) | 00:04:00 |
| * 73 | HASH JOIN | | 1884 | 248K | | 6435 (18) | 00:01:18 |
| * 74 | HASH JOIN | | 1884 | 226K | 9320K | 4206 (27) | 00:00:51 |
| 75. VIEW | STAG_MANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| 76. MAT_VIEW FULL ACCESS | STAG_AANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| * 77 | MAT_VIEW FULL ACCESS | STAG_ANAME_MV | 113K | 10 M | | 1085 (2) | 00:00:14 |
| 78. VIEW | STAG_MASTER_VW | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 79 | MAT_VIEW FULL ACCESS | STAG_MASTER_MV | 39985 | 468K | | 2229 (1) | 00:00:27 |
| 80. VIEW | ABC_CDE_INDEX_AST_VW | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 81 | TABLE ACCESS FULL | ABC_CDE_INDEX_AST | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| 82. VIEW | STAG_NAMADDS_VW | 248K | 6316K | | 872 (1) | 00:00:11 |
| 53 M | MAT_VIEW FULL ACCESS | STAG_NAMADDS_MV | 248K | 6316K | | 872 (1) | 00:00:11 |
| 84. VIEW | ABC_CDE_INDEX_CHG_VW | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 85 | TABLE ACCESS FULL | ABC_CDE_INDEX_CHG | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 86 | OUTER HASH JOIN | | 560. 128K | | 23267 (6) | 00:04:40 |
| * 87. HASH JOIN | | 162. 35964 | | 20816 (6) | 00:04:10 |
| * 88. OUTER HASH JOIN | | 95. 18620 | | 19942 (7) | 00:04:00 |
| * 89 | HASH JOIN | | 94. 12690 | | 6435 (18) | 00:01:18 |
| * 90 | HASH JOIN | | 94. 11562 | 9320K | 4206 (27) | 00:00:51 |
| 91. VIEW | STAG_MANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| 92. MAT_VIEW FULL ACCESS | STAG_AANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| * 93 | MAT_VIEW FULL ACCESS | STAG_ANAME_MV | 113K | 10 M | | 1085 (2) | 00:00:14 |
| 94. VIEW | STAG_MASTER_VW | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 95 | MAT_VIEW FULL ACCESS | STAG_MASTER_MV | 39985 | 468K | | 2229 (1) | 00:00:27 |
| 96. VIEW | ABC_CDE_INDEX_AST_VW | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 97 | TABLE ACCESS FULL | ABC_CDE_INDEX_AST | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| 98. VIEW | STAG_NAMADDS_VW | 248K | 6316K | | 872 (1) | 00:00:11 |
| 99. MAT_VIEW FULL ACCESS | STAG_NAMADDS_MV | 248K | 6316K | | 872 (1) | 00:00:11 |
| 100. VIEW | ABC_CDE_INDEX_CHG_VW | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 101 | TABLE ACCESS FULL | ABC_CDE_INDEX_CHG | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 102 | OUTER HASH JOIN | | 28. 6580. | 23267 (6) | 00:04:40 |
| * 103 | HASH JOIN | | 8. 1776 | | 20816 (6) | 00:04:10 |
| * 104 | OUTER HASH JOIN | | 5. 980. | 19942 (7) | 00:04:00 |
| * 105 | HASH JOIN | | 5. 675. | 6435 (18) | 00:01:18 |
| * 106 | HASH JOIN | | 5. 615 | 9320K | 4206 (27) | 00:00:51 |
| 107. VIEW | STAG_MANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| 108. MAT_VIEW FULL ACCESS | STAG_AANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| * 109 | MAT_VIEW FULL ACCESS | STAG_ANAME_MV | 113K | 10 M | | 1085 (2) | 00:00:14 |
| 110. VIEW | STAG_MASTER_VW | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 111 | MAT_VIEW FULL ACCESS | STAG_MASTER_MV | 39985 | 468K | | 2229 (1) | 00:00:27 |
| 112. VIEW | ABC_CDE_INDEX_AST_VW | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 113 | TABLE ACCESS FULL | ABC_CDE_INDEX_AST | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| 114. VIEW | STAG_NAMADDS_VW | 248K | 6316K | | 872 (1) | 00:00:11 |
| 115. MAT_VIEW FULL ACCESS | STAG_NAMADDS_MV | 248K | 6316K | | 872 (1) | 00:00:11 |
| 116. VIEW | ABC_CDE_INDEX_CHG_VW | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 117 | TABLE ACCESS FULL | ABC_CDE_INDEX_CHG | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 118 | OUTER HASH JOIN | | 1. 235. | 23267 (6) | 00:04:40 |
| * 119 | OUTER HASH JOIN | | 1. 174. | 9760 (12) | 00:01:58 |
| * 120 | HASH JOIN | | 1. 161. | 7309 (16) | 00:01:28 |
| * 121 | HASH JOIN | | 1. 135. | 6435 (18) | 00:01:18 |
| * 122 | HASH JOIN | | 1. 123 | 9320K | 4206 (27) | 00:00:51 |
| 123 | VIEW | STAG_MANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| 124. MAT_VIEW FULL ACCESS | STAG_AANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| * 125 | MAT_VIEW FULL ACCESS | STAG_ANAME_MV | 113K | 10 M | | 1085 (2) | 00:00:14 |
| 126. VIEW | STAG_MASTER_VW | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 127 | MAT_VIEW FULL ACCESS | STAG_MASTER_MV | 39985 | 468K | | 2229 (1) | 00:00:27 |
| 128. VIEW | STAG_NAMADDS_VW | 248K | 6316K | | 872 (1) | 00:00:11 |
| 129. MAT_VIEW FULL ACCESS | STAG_NAMADDS_MV | 248K | 6316K | | 872 (1) | 00:00:11 |
| 130. VIEW | ABC_CDE_INDEX_CHG_VW | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 131 | TABLE ACCESS FULL | ABC_CDE_INDEX_CHG | 818K | 10 M | | 2448 (1) | 00:00:30 |
| 132. VIEW | ABC_CDE_INDEX_AST_VW | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 133 | TABLE ACCESS FULL | ABC_CDE_INDEX_AST | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 134 | OUTER HASH JOIN | | 1. 235. | 23267 (6) | 00:04:40 |
| * 135 | OUTER HASH JOIN | | 1. 174. | 9760 (12) | 00:01:58 |
| * 136 | HASH JOIN | | 1. 161. | 7309 (16) | 00:01:28 |
| * 137 | HASH JOIN | | 1. 135. | 6435 (18) | 00:01:18 |
| * 138 | HASH JOIN | | 1. 123 | 9320K | 4206 (27) | 00:00:51 |
| 139. VIEW | STAG_MANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| 140. MAT_VIEW FULL ACCESS | STAG_AANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| * 141 | MAT_VIEW FULL ACCESS | STAG_ANAME_MV | 113K | 10 M | | 1085 (2) | 00:00:14 |
| 142. VIEW | STAG_MASTER_VW | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 143 | MAT_VIEW FULL ACCESS | STAG_MASTER_MV | 39985 | 468K | | 2229 (1) | 00:00:27 |
| 144. VIEW | STAG_NAMADDS_VW | 248K | 6316K | | 872 (1) | 00:00:11 |
| 145. MAT_VIEW FULL ACCESS | STAG_NAMADDS_MV | 248K | 6316K | | 872 (1) | 00:00:11 |
| 146. VIEW | ABC_CDE_INDEX_CHG_VW | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 147 | TABLE ACCESS FULL | ABC_CDE_INDEX_CHG | 818K | 10 M | | 2448 (1) | 00:00:30 |
| 148. VIEW | ABC_CDE_INDEX_AST_VW | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 149 | TABLE ACCESS FULL | ABC_CDE_INDEX_AST | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 150 | OUTER HASH JOIN | | 1. 235. | 23267 (6) | 00:04:40 |
| * 151 | OUTER HASH JOIN | | 1. 174. | 9760 (12) | 00:01:58 |
| * 152 | HASH JOIN | | 1. 161. | 7309 (16) | 00:01:28 |
| * 153 | HASH JOIN | | 1. 135. | 6435 (18) | 00:01:18 |
| * 154 | HASH JOIN | | 1. 123 | 9320K | 4206 (27) | 00:00:51 |
| 155. VIEW | STAG_MANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| 156. MAT_VIEW FULL ACCESS | STAG_AANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| * 157 | MAT_VIEW FULL ACCESS | STAG_ANAME_MV | 113K | 10 M | | 1085 (2) | 00:00:14 |
| 158. VIEW | STAG_MASTER_VW | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 159 | MAT_VIEW FULL ACCESS | STAG_MASTER_MV | 39985 | 468K | | 2229 (1) | 00:00:27 |
| 160. VIEW | STAG_NAMADDS_VW | 248K | 6316K | | 872 (1) | 00:00:11 |
| 161. MAT_VIEW FULL ACCESS | STAG_NAMADDS_MV | 248K | 6316K | | 872 (1) | 00:00:11 |
| 162. VIEW | ABC_CDE_INDEX_CHG_VW | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 163 | TABLE ACCESS FULL | ABC_CDE_INDEX_CHG | 818K | 10 M | | 2448 (1) | 00:00:30 |
| 164. VIEW | ABC_CDE_INDEX_AST_VW | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 165 | TABLE ACCESS FULL | ABC_CDE_INDEX_AST | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 166 | OUTER HASH JOIN | | 1. 235. | 37689 (26) | 00:07:33 |
| * 167 | HASH JOIN | | 1. 222. | 35237 (28) | 00:07:03 |
| * 168 | HASH JOIN | | 1. 210 | | 33008 (29) | 00:06:37 |
| * 169 | HASH JOIN | | 9781. 1776K | | 22622 (1) | 00:04:32 |
| * 170 | FILTER | | | | | | |
| * 171 | OUTER HASH JOIN | | 5716 | 893K | 12 M | 21748 (1) | 00:04:21 |
| * 172 | MAT_VIEW FULL ACCESS | STAG_ANAME_MV | 113K | 10 M | | 1085 (2) | 00:00:14 |
| 173. VIEW | ABC_CDE_INDEX_AST_VW | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| * 174 | TABLE ACCESS FULL | ABC_CDE_INDEX_AST | 1898K | 110 M | | 13499 (1) | 00:02:42 |
| 175. VIEW | STAG_NAMADDS_VW | 248K | 6316K | | 872 (1) | 00:00:11 |
| 176. MAT_VIEW FULL ACCESS | STAG_NAMADDS_MV | 248K | 6316K | | 872 (1) | 00:00:11 |
| * 177 | VIEW | STAG_MANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| 178. MAT_VIEW FULL ACCESS | STAG_AANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| 179. VIEW | STAG_MASTER_VW | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 180 | MAT_VIEW FULL ACCESS | STAG_MASTER_MV | 39985 | 468K | | 2229 (1) | 00:00:27 |
| 181. VIEW | ABC_CDE_INDEX_CHG_VW | 818K | 10 M | | 2448 (1) | 00:00:30 |
| * 182 | TABLE ACCESS FULL | ABC_CDE_INDEX_CHG | 818K | 10 M | | 2448 (1) | 00:00:30 |
| 183. LOAD SELECT ACE | SYS_TEMP_0FD9FCB73_F58FAD20 | | | | | |
| 184. VIEW | | 145K | 18 M | | 187 M (1) | 625:08:34 |
| 185. UNIQUE FATE | | 145K | 22 M | 1215G | 187 M (1) | 625:08:34 |
| * 186 | HASH JOIN | | 7487M | 1122G | | 274K (98) | 00:54:59 |
| 187. VIEW | STAG_MASTER_VW | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 188 | MAT_VIEW FULL ACCESS | STAG_MASTER_MV | 39985 | 468K | | 2229 (1) | 00:00:27 |
| * 189 | HASH JOIN | | 7487M | 1039G | 9320K | 245K (98) | 00:49:06 |
| 190. VIEW | STAG_MANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| 191. MAT_VIEW FULL ACCESS | STAG_AANAME_MV | 264K | 6208K | | 974 (1) | 00:00:12 |
| * 192 | HASH JOIN | | 248K | 29 M | 9240K | 2995 (1) | 00:00:36 |
| 193. VIEW | STAG_NAMADDS_VW | 248K | 6316K | | 872 (1) | 00:00:11 |
| 194. MAT_VIEW FULL ACCESS | STAG_NAMADDS_MV | 248K | 6316K | | 872 (1) | 00:00:11 |
| * 195 | MAT_VIEW FULL ACCESS | STAG_ANAME_MV | 113K | 10 M | | 1075 (1) | 00:00:13 |
| 196. UNIQUE FATE | | 352K | 60 M | 72 M | 17677 (12) | 00:03:33 |
| 197. UNION-ALL | | | | | | |
| * 198 | VIEW | | 352K | 60 M | | 1883 (1) | 00:00:23 |
| 199. TABLE ACCESS FULL | SYS_TEMP_1234_5678 | 352K | 60 M | | 1883 (1) | 00:00:23 |
| * 200 | FILTER | | | | | | |
| * 201 | OUTER HASH JOIN | | 1. 150. | 1982 (1) | 00:00:24 |
| * 202 | HASH JOIN | | 1. 142. | 97 (2) | 00:00:02 |
| 203. VIEW | | 11540 | 92320 | | 48 (0) | 00:00:01 |
| 204. TABLE ACCESS FULL | SYS_TEMP_3456_0987F0 | 11540 | 1 510 K | | 48 (0) | 00:00:01 |
| 205. VIEW | | 11540 | 1 510 K | | 48 (0) | 00:00:01 |
| 206. TABLE ACCESS FULL | SYS_TEMP_0987F0_3456 | 11540 | 1 510 K | | 48 (0) | 00:00:01 |
| 207. VIEW | | 352K | 2757K | | 1883 (1) | 00:00:23 |
| 208. TABLE ACCESS FULL | SYS_TEMP_09kjhn0_3456 | 352K | 60 M | | 1883 (1) | 00:00:23 |
-----------------------------------------------------------------------------------------------------------------------
{code}
Thank you.
Well, that was just a guess because you don't want to share the query, nor execution plan with actual cardinalities. The goal is probably to avoid the separate.
-
Help with the query to select only one record from the result set in double
Hello
Please help with the query. Version of Oracle database we use is 10g R2.
I have a vision that is duplicated IDS, but they are used across the different functions. See below examples of data. Please help me with a query to select only one record (based on ID regardless of the area) from the bottom of the result set of duplicate records. For what is the point of view is there unique records, given the combination of the fields ID, Org, DF, dry, Sub-Sec
ID Org DF Sec Sub-Sec (163) CQ CPDM CPDM HD (163) PC ENG ENG ENG (163) CQ ASIC ASIC IS 8888 TS TAC TAC TAC (163) TS HE HE SW 6789 CQ INFO INFO FOS 6789 PC SECSYS SECSYS INFO1 6789 TS SECSYS SECSYS INFO2 9009 PC BMS BMS BMS1 My result set must eliminate the duplicate identifiers regardless of whoever we choose of the result set. (I mean without distinction Org, DF, s, Sub-s). My expected result set should be.
ID DSB DF SEC Sub-Sec (163) CQ CPDM CPDM HD 8888 TS TAC TAC TAC 6789 CQ INFO INFO FOS 9009 PC BMS BMS BMS1 Thank you
Orton
Hello
This sounds like a job for ROW_NUMBER:
WITH got_r_num AS
(
SELECT id, DSB, df, s, sub_sec org
ROW_NUMBER () OVER (PARTITION BY ID.
ORDER BY org
) AS r_num
OF view_x
)
SELECT id, DSB, df, sub_sec s,
OF got_r_num
WHERE r_num = 1
;
He is a Top - N query example, where you choose the elements of N (N = 1 in this case) from the top of an ordered list.
I hope that answers your question.
If not, post a small example of data (CREATE TABLE and INSERT, only relevant columns instructions) to your sample data and the results desired from these data. (I know that you said that you were a view selection. Just for this thread, pretending it is a picture and post simple CREATE TABLE and INSERT statements to simulate your point of view).
Point where the above query is to produce erroneous results, and explain, using specific examples, how you get the right results from data provided in these places. (I didn't quite understand the explanation above. I don't know why you want toID ORG DF DRY SUB_SEC
-- --- -- --- -------
1234 CQ DPRK DPRK HD
and is not
1234 IS CQ ASIC, ASIC
or
TS 1234 IT IT SW
or
1234 CQ ASIC ASIC HD
)
If you change the query at all, post your modified version.
Always say what version of Oracle you are using (for example, 11.2.0.2.0).See the FAQ forum: https://forums.oracle.com/message/9362002
-
Filter the table display of the query object (it can a bug in jdev 12)
Hello:
I found an error/bug possible in jdeveloper 12 c when I migrate my application of jdev 11g.
To test this issue, I did the same test request in jdeveloper 11g and jdeveloper 12 c (to avoid to migrate the process).
Project template
-Create a display of the query object. Code:
SELECT 1 CODE, 100 DESCRIPTION FROM DUAL UNION ALL SELECT 2 CODE, 200 DESCRIPTION FROM DUAL
-Create a Module of the Application, and then drag this point of view in.
ViewController project
-Create a page and drag in the criteria named 'All searchable attributes' of the previous ViewObject as "ADF table filtered.
-Run the application
Results:
On jdeveloper 11g, however it makes the filter above the table box in jdev not 12 c.
Is this a bug or I need to select something in jdev12c to get the same functionality?
Yes, known bug 17279781. It is currently scheduled for a 12.1.4 fix. If this issue is crucial to you, please file an SR, mentioning the bug number and indicate your reasons for wanting a fix as soon as possible.
Note there is a solution:
To work around the problem, you can configure the filter yourself by adding an af:inputText
facet filter columns and bind the inputText property value to the EL
#{vs.filterCriteria.
}. The page to rerun the filter for the column look and work.
CM.
-
use F8 & F10 keys on the keyboard to run the query and save a form
I created a screen. Here I can save by pressing CTRL + S (written a validation key trigger) or the button Save, I placed.
Now the user want to F10 to save & key F8 to run the query.
How can I do? Should what trigger I write the code...
I use oracle 10g and oracle developer suite 10 g.
I have fmrweb.res as follows:-
9: 0: 'Tab': 1: "then on the ground."
9: 2: "Ctrl + Tab": 1: "then on the ground."
9: 1: "Shift + Tab": 2: "previous field.
9: 3: 'Shift + Ctrl + Tab': 2: "previous field.
85: 2: "Ctrl + U": 3: "clear the field".
38: 0: 'Up': 6: 'Up '.
40: 0: 'Down': 7: "Down".
33: 0: 'PG': 12: "scroll to top".
34: 0: "PageDown": 13: "scroll."
69: 2: 'Ctrl + E': 22: 'Edit '.
10: 0: "Enter": 27: «Back»
120: 0: 'F9': 29: "list of values".
76: 2: "Ctrl + L": 29: "list of values".
81: 2: 'Ctrl + Q': 32: "Exit".
75: 2: "Ctrl + K": 35: 'display keys '.
112: 2: 'Ctrl + F1': 35: 'display keys '.
83: 2: 'Ctrl + S': 36: 'engage '.
121: 2: "F10": 36: 'engage '.
114: 1: 'SHIFT + F3': 61: 'next primary key '.
115: 1: "SHIFT + F4": 62: "delete folder".
117: 1: "SHIFT + F6": 63: 'delete folder '.
115: 0: "F4": 64: "Double registration".
117: 0: 'F6': 65: "insert record".
119: 1: "SHIFT + F8": 66: "a next Recordset.
1005: 0: 'Down': 67: "then save.
1004: 0: 'Up': 68: "history".
40: 1: 'Shift + down': 67: "then save.
38: 1: "shift + up": 68: "history".
116: 1: "Shift + F5": 69: 'clear the block '.
116: 0: 'F5': 70: "block the Menu."
34: 1: "shift + page down": 71: 'then block '.
33: 1: ' shift + Pg. Prev ': 72: "previous block.
34: 2: "Ctrl + PG. Next": 71: 'then block '.
33: 2: "Ctrl + PG. Prev': 72: "previous block.
114: 0: "F3": 73: "duplicate field '.
118: 1: "Shift + F7": 74: 'clear form '.
118: 0: "F7": 76: "enter the query."
119: 0: 'F8': 77: 'execute the query. "
122: 0: 'F11': 76: "enter the query."
122: 2: "Ctrl + F11": 77: 'execute the query. "
112: 1: "SHIFT + F1": 78: "error to display.
80: 2: 'Ctrl + P': 79: 'print '.
113: 1: "SHIFT + F2": 80: "request Count".
123: 0: "F12": 81: "update file".
121: 3: 'Shift + Ctrl + F10': 82: "function 0".
112: 3: 'Shift + Ctrl + F1': 83: «Function 1"»
113: 3: 'Shift + Ctrl + F2': 84: «Function 2"»
114: 3: 'Ctrl + Shift + F3': 85: «function 3"»
115: 3: 'Shift + Ctrl + F4': 86: «function 4"»
116: 3: 'Shift + Ctrl + F5': 87: «Function 5"»
117: 3: 'Shift + Ctrl + F6': 88: «function 6"»
118: 3: 'Shift + Ctrl + F7': 89: «Function 7"»
119: 3: 'Shift + Ctrl + F8': 90: «Function 8"»
120: 3: 'Shift + Ctrl + F9': 91: «Function 9"»
113: 0: 'F2': 95: "list of tab Pages.
72: 2: "Ctrl + H": 30: "Help".
112: 0: 'F1': 30: "Help".
Please suggest...Hello.
First of all check that you have set "term" among others in the variable 'otherparams' in formsweb.cfg
For example:
otherparams = expression = term %
Then make sure that you put the correct path for the keyboard mapping file in the variable "term" as I wrote in the previous post.
Things should work as I did several times.
Best regards.
-
Rewrite the query, select below or try to get the necessary O/P
Hello..
My example of data.,.
Create table customer (name varchar2 (10), telephone1 telephone2 number (10), number of phone3 (10), (10) number, bitwisephone number (10));
Insert into customer values('a',23456,67890,null,12345);
Insert into customer values ('b', 67459,89760,null, 37689);
create table do_not_call (dont_call number (10));
insert into do_not_call values (67890);
insert into do_not_call values (37689);
Question: -.
--------------
Customer 'a' has value of numbers1 as 23456.check if telephone1 exists in the do_not_call table.
In fact there is no, so set the bit for numbers1 as "o" like wise search telephone2
& phone3.after update of the bitwisephone for each client should be as the output below.
Need to O/P: -.
-------------------
name bitwisephone
a 010
b 001
For that matter... I use "any" operator...
SELECT name, case when numbers1 = all (SELECT dont_call FROM do_not_call) and then put an end to '1' other '0'.
-case when telephone2 = all (SELECT dont_call FROM do_not_call) and then put an end to '1' other '0'.
-case when phone3 = all (SELECT dont_call FROM do_not_call) then '1' other '0' end 'Bits '.
OF THE customer;
Is there any other way to get the necessary O/P?
Thank you!!
Kind regards
VijayRajaram.Looks like one already answered Re: rewrite the query, select below or try to get the necessary O/P
with customer(name,phone1,phone2,phone3,bitwisephone) as (select 'a',23456,67890,12345,null from dual union all select 'b',67459,89760,37689,null from dual ), do_not_call(dont_call) as (select 67890 from dual union all select 23456 from dual union all select 37689 from dual ) select name, to_char(mod(trunc(sum(weight)/4),2))|| to_char(mod(trunc(sum(weight)/2),2))|| to_char(mod(sum(weight),2)) bitwisephone from (select name,phone1 phone,4 weight from customer union all select name,phone2,2 from customer union all select name,phone3,1 from customer ) c, do_not_call d where c.phone = d.dont_call(+) and d.dont_call is not null group by namePlease do not duplicate messages
Concerning
Etbin
-
Result of the query based on the form of the parameter
Good morning people. I really couldn't come up with a smart enough subject line, but I'll try and make up the body.
I currently have a report that accepts parameters on the parameter form. They are extra employees and Number of Copies. The employee ID is stored in the Employee table, but the number of copies is not.
The output of the report shows all the different addresses and phone numbers, the employee a. lets say, Employee ID 0001 has two addresses - home and office. In the report of my request, he'll give me two records in the repeating group. However, I have another parameter and the ID of the employee who is the number of Copies. In this case, if the number of Copies to be printed is 1, so it isn't a problem. However, if the Number of Copies is entered by the user is 4, I think in this case 4 x 2 = 8 pages of report output (4 with the address of the House) and 4 with the address of the office.
I know there is a way to do this using a temporary table in AfterPForm and then using the results of the query by joining my request to the temporary table, but I was really hoping to avoid this situation if it can be treated through the query.
Main request:
Any help is appreciated. Thank you!SELECT e.emp_no, e.saln||e.first_name||' '||e.last_name emp_name, a.street, a.city||' '||a.province||' '||a.postal_code city, '('||a.tel_area||') '||a.tel_number telephone FROM employee e, emp_address a WHERE e.emp_no = a.emp_no AND e.emp_no = :P_EMP_NO;Hello
Since you started a new thread in the forum SQL and PL/SQL {message identifier: = 10470358}, please mark this thread as "Answered" right away.
Maybe you are looking for
-
Buy the show with another country
Hello! First of all, thank you for taking the time to read about me. So, I live in the US and my parents live in Mexico; recently (this week) I've gifted them a TV series via iTunes. My mother has an iTunes account in the Mexico and she received the
-
How can I get the backlight to work on the keyboard?
-
Pavilion dv6t - b 6, 00 QJ912AV: I need a new fan/radiator! I don't know which.
I have a HP Paviliion dv6 Model: dv6t - b 6, 00 Product: QJ912AV Series: (deleted content) Running Windows 7 Home Premium Intel Core i7 Radeon (TM) HD 6490 M From what I understand, I'm running an Intel processor and a graphics subsystem with discret
-
Update of RAM and processor? HP Pavilion dv7 FP873EA - Vista 32-bit
Hey there, Is it possible that I could upgrade this laptop, it's a good old classic, but I don't want to buy a new one thinking yet, if may be upgraded, unless it will cost more than a new If there is anyway to upgrade of RAM and the processor for th
-
How to mark a file mp3, audiobooks
I use my Clip + to download and listen to audio books from Overdrive libraray. Periodically, some books will download correctly, but when I transfer them to the player (using a Mac) they places in the music/books/unknown file. Today, I downloaded 2 b