This is actually a really bad thing to do IMHO, and it's not supported in most other database platforms.
The reasons people do it:
they're lazy - I don't know why people think their productivity is improved by writing terse code rather than typing for an extra 40 milliseconds to get much more literal code.
The reasons it's bad:
it's not self-documenting -...
The most likely cause of a mutating table error is the misuse of triggers. Here is a typical example:
you insert a row in table A
a trigger on table A (for each row) executes a query on table A, for example to compute a summary column
Oracle throws an ORA-04091: table A is mutating, trigger/function may not see it
This is an expected and normal behaviour, ...
Oracle's official documentation library has some great resources, including:
The Database Concepts guide, which is essential reading for beginner and Oracle ninja alike.
The 2 Day DBA
The 2 Day Developer's Guide
Oracle 12c official PL/SQL documentation:
PL/SQL Language Reference
PL/SQL Packages and Types Reference
Chapter 5 Developing Stored Subprograms ...
The code you posted is using a cursor. It is using an implicit cursor loop.
There are cases where using an explicit cursor loop (i.e. declaring a CURSOR variable in the declaration section) produces either cleaner code or better performance
If you have more complex queries that you can't refactor out into views, it can make the code easier to read if your ...
If you're really only looking to learn about the development side and have no interest in the administration or installation side at the moment, a quicker route might be to download a prebuilt developer VM image for Virtualbox. That can get you up and running very quickly, and you can connect to the DB running inside the VM from outside, so you can continue ...
Anonymous PL/SQL blocks don't start with IF. The above code should be in between a begin and end; at least.
EXISTS is an SQL function, it can't be used in PL/SQL like that.
Try something like this:
set serveroutput on
select count(*) into c from my_table where rownum = 1;
if c != 0 then
Benefits of Packages
Logical Grouping – Methods that work together can be put into a cohesive unit rather than just logically coupled but physically separate.
Secure Private Methods - Functions and Procedures can be made private to the package and only be used within it. This makes the public surface simpler and more secure.
Privilege Management – ...
You can do this with DBMS_LOCK and an exclusive lock.
See the following procedure:
CREATE OR REPLACE PROCEDURE myproc
This is not an Oracle or PL/SQL issue, but a matter of implementing the proper algorithm.
Here is an example:
CREATE OR REPLACE FUNCTION dec2bin (N in number) RETURN varchar2 IS
N2 number := N;
while ( N2 > 0 ) loop
binval := mod(N2, 2) || binval;
N2 := trunc( N2 / 2 );
As you can see from the output below, a test anonymous PL/SQL block works in SQL Plus as expected:
[oracle@node1 ~]$ sqlplus phil/phil
SQL*Plus: Release 22.214.171.124.0 Production on Mon Oct 1 21:55:35 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Oracle Database 11g Enterprise Edition Release 126.96.36.199.0 - 64bit Production
Of course you ought to study the license, but as I recall it is free to download and use for non-production purposes.
It includes all of the Option packs, and is not in any sense cripled, but patches will not be available as they would be if you had a support account.
Oracle XE is free to use in production environments, but has limited functionality and ...
First, if you are creating a procedure in a package, the package name will need to be included when you call the procedure.
should correctly invoke your procedure.
Second, you have issues with the naming of your local variables. Normally, you would not create local variables like city and postal_number that are the ...
A mutating table occurs when a statement causes a trigger to fire and that trigger references the table that caused the trigger. The best way to avoid such problems is to not use triggers, but I suspect the DBA didn’t take the time to do that. He could have done one of the following:
Changed the trigger to an after trigger.
Changed it from a row level ...
MySQL allows you to do GROUP BY with aliases (Problems with Column Aliases). This would be far better that doing GROUP BY with numbers.
Some people still teach it
Some have column number in SQL diagrams. One line says: Sorts the result by the given column number, or by an expression. If the expression is a single parameter, then the value is interpreted as ...
I think people were having trouble understanding your question due to the table structure which is so bad it seems designed to give you a headache.
As Balazs Papp indicates very little can be implemented that will scale or not look like something hacked together.
However there are solutions that can be done in PL/SQL. A pipelined table function will end ...
Fortunately, I found in the existing PL/SQL code I have to maintain, a working "native" behavior:
V_COUNT := MY_ARRAY.COUNT;
should do the trick.
This one is very hard to find with Google, since "count" is more frequently referring to the SELECT COUNT(...) which can be found in SQL queries...
Interesting question. As far as I can tell, this is not possible, though it seems like it should be. Unless someone else can show how it can be done, a workaround would be to nest the code in a block:
create or replace trigger trg_before_insert_temp1 before insert on temp1 for each row
Gathering statistics and rebuilding indexes are two completely separate things.
It is exceedingly rare that an index in Oracle needs to be rebuilt so any process that is regularly rebuilding an index is highly suspect. I strongly suspect that rebuilding the indexes is unnecessary. And I would strongly suggest spending some quality time reading through ...
Is there some operator or function that can give me the indices of the array
No, you have to loop through the associative array:
type a_arr_t is table of PLS_INTEGER index by PLS_INTEGER;
type keys_t is table of PLS_INTEGER;
keys_ keys_t := keys_t();
a_arr(1) := 2;
This is the expected behaviour of nextval as documented:
Within a single SQL statement containing a reference to NEXTVAL, Oracle increments the sequence once:
For each row returned by the outer query block of a SELECT statement
[...] If any of these locations contains more than one reference to NEXTVAL, then Oracle increments the sequence ...
I would just delete.
Even if I had to only delete if there were say exactly 2 records, then I would add this condition to the where clause, like
DELETE FROM table1
AND (SELECT COUNT(*) FROM table1 WHERE col1 = 'somevalue') = 2;
In all cases when writing a delete statement consider that in general the where clause is usually either
Have you seen this? https://community.oracle.com/thread/889338?start=0&tstart=0
It states you can only exchange partitions from a partitioned table to a non-partitioned table, or vice-versa.
You'd need to temporarily exchange the partition into an
interim, non-partitioned, table, then into the target partitioned table.
There are some interesting ...
In SQL Developer, use the /*insert*/ "hint".
select /*insert*/ * from t1;
REM INSERTING into T1
SET DEFINE OFF;
Insert into T1 (C1,C2) values (1,2);
Insert into T1 (C1,C2) values (2,3);
Insert into T1 (C1,C2) values (3,4);
Another useful "hint":
select /*csv*/ * from t1;
Starting with version 4.1, the "hint" the below also works:
From a general perspective (not platform-specific), here's what I'd recommend mastering for data warehouse projects:
Know how to load data fast. BI projects usually involve nightly loads of large amounts of data. The ETL guys need to shove data in fast with a minimum of concurrency issues. This means knowing when to disable indexes, when to perform tasks ...
Oracle has Java server-side, but I'd caution that it is not a replacement for PL/SQL. There is no better language than PL/SQL for manipulating data stored in the database - Java may be appropriate for computationally intensive business logic.
There are currently four procedural languages available in the standard PostgreSQL distribution: PL/...