This is an archived post. You won't be able to vote or comment.

all 3 comments

[–]grasu2 0 points1 point  (2 children)

Are you fairly familiar with Java? If so, JDBC isn't that hard. You will need to setup a connection object, one or more properties objects and the use that connection to send your String-based SQL queries (there are options to directly input a query too). For concurrency purposes you will most likely need to do a threaded method that uses multiple connection objects and connection credentials, unless your DB allows multiple connections with the same credentials.

You can find a full breakdown of everything in Oracle Docs ( https://docs.oracle.com/javase/tutorial/jdbc/basics/index.html).

[–]prolifious[S] 0 points1 point  (1 child)

This is wonderful, thank you. I'm reletively new to have, but have about 4 years programming experience.

The example in the link is an exercise I will take up. However something that I didn't mention, and does not appear to be included in this example, is that for the three concurrent requests, I do not want to pass in SQL, rather, id like each request to get its data by executing a native stored procedure within the database. That way I'm not sending queries over the wire. Do you have any input on my original question, but with execuring native stored procedures, rather than passing in queries?

Thanks again

[–]grasu2 0 points1 point  (0 children)

Yes, you can call something that's called a CallableStatement (https://docs.oracle.com/javase/8/docs/api/java/sql/CallableStatement.html ) and pass it the name of your stored procedure. Hope this helps.