“rowtype” here is an Oracle PL/SQL-specific type, I don’t think it would be supported by JDBC. A quick search of the oracle forums (google “jdbc rowtype site:oracle.com”) suggests the same. You’re probably better off returning a cursor, or just execute the SQL from JDBC directly.
All entries tagged oracle.
You can subscribe to an RSS feed of this list.
Dec 2011
-
Reply to:
Jul 2010
-
Reply to:
Try something like this:
insert into onTeam(date, player, teamName) select 'newDate','Matt Holliday', teamName from onTeam where player = 'Matt Holliday'
Mar 2010
-
Reply to:
MINUS is the same as saying “get all the rows of the first query, then from that set remove the rows that are also in the second query”, so you could like load the results from the first query into an array in-memory, then loop through the second query results and check them one-by-one against the first query results and remove them if they exist.
I’m not sure that will actually perform better though (depends on a lot of things). You might also want to consider using NOT EXISTS instead and check that performance, i.e.
SELECT RTRIM(LTRIM(A.HEAD)), A.EFFECTIVE_DATE, FROM TABLE_1 A WHERE A.TYPE_OF_ACTION='6' AND A.EFFECTIVE_DATE >= ADD_MONTHS(SYSDATE,-15) AND NOT EXISTS ( SELECT 1 fFROM TABLE_2 B WHERE RTRIM(LTRIM(A.HEAD)) = RTRIM(LTRIM(B.HEAD)) AND A.EFFECTIVE_DATE = B.EFFECTIVE_DATE )
Some functional indexing may also be needed on RTRIM(LTRIM(A.HEAD))
Jan 2010
-
I know the oci driver can perform transparent failover of the database, but does the thin driver have the same capability?
Dec 2009
-
Reply to:
It means that any single SQL statement you run is atomic in nature - it will either succeed completely or fail completely. If your SQL statement fails, and triggers that would have run as a result of that SQL statement will fail as well.
-
Reply to:
Try “where length(column) < lengthb(column)”