Named parameters support

where can i get another driver except the ( JdbcOdbcDriver )
as it doesn`t support named parameters in the CallableStatement
Thanks

http://industry.java.sun.com/products/jdbc/drivers

Similar Messages

NOT Using Named Parameters in a Native Query

Hi!
like it is written in the Toplink JPA Extensions reference Toplink supports using named parameters in native queries.
See example from http://www.oracle.com/technology/products/ias/toplink/jpa/resources/toplink-jpa-extensions.html:
Example 1-11 Specifying a Named Parameter With #
Query queryEmployees = entityManager.createNativeQuery(
"SELECT OBJECT(emp) FROM Employee emp WHERE emp.firstName = #firstname"
queryEmployeeByFirstName.setParameter("firstName", "Joan");
Collection employees = queryEmployees.getResultList();
But I want to use "#" in the SQL statement so I want to disable this parameter binding somehow and let the query just execute the SELECT statement I deliver.
I have tried to add the property
<property name="toplink.jdbc.bind-parameters" value="false"/>
into the persistence.xml and I have also tried to add the query hint
query.setHint(TopLinkQueryHints.BIND_PARAMETERS, HintValues.FALSE);
but none of them prevents the # to be uses as a paramter. this causes the exception:
Exception [TOPLINK-6132] (Oracle TopLink Essentials - 9.1 (Build b22)): oracle.toplink.essentials.exceptions.QueryException
Exception Description: Query argument ######' not found in list of parameters provided during query execution.
Query: ReadAllQuery(de.merck.compas.material.SimilarLocalMaterialListItemBV)
The SQL Statement is
SELECT * FROM TABLE (
CAST ( RCGC.PHA_P_COMPASMDM.LookupSimilarMats
( 'COC003','10021500150000000997','30','30','040','standard','','001001','001001','123456','##########','X','X','X','X','U' )
AS RCGC.PHA_COMPAS_SIMILAR_MATS ) )
I am using the latest Toplink essentials build together with an Oracle 9.2i DB in a Java SE web application.
Can anyone give me a little hint what to do?
Thanks and best regards,
Alex

I hope this is what you need:
[TopLink Fine]: 2007.01.19 02:56:48.278--ServerSession(17712783)--Connection(723185)--Thread(Thread[http-8080-Processor2
3,5,main])--SELECT APPL_CGP_MATLOC, CHANGE_REQ_MATLOC, CD_PHA_MAT_LOC, LCOMP, LOC_MAT_NAME, APPL_GDM_MATLOC, LOC_MAT_NAM
E_SHORT, APPL_PDW_MATLOC, PHA_MAT_LOC_LCOMMENT, APPL_TP_MATLOC, DIVISION, APPL_WRS_MATLOC, ARTICLE_ID_MDA, LU_PHA_MAT_LO
C, LOC_MAT_NAME_OLD, LDT_PHA_MAT_LOC, PHA_MAT_LOC_STATUS, CU_PHA_MAT_LOC, MAT_LOC_ID, RCOMP, MAT_ID FROM RCGC.PHA_V_COMP
AS_MAT_MATLOC WHERE ((MAT_LOC_ID = '123456') AND (RCOMP = '001001'))
[TopLink Fine]: 2007.01.19 02:56:48.398--ServerSession(17712783)--Connection(32404901)--Thread(Thread[http-8080-Processo
r23,5,main])--SELECT MAT_ID, DESCRIPTION, PHA_MATERIAL_LCOMMENT, PACKSIZE, LU_PHA_MATERIAL, PACKSIZE_UNIT, LDT_PHA_MATER
IAL, CONTAINER_NAME, CU_PHA_MATERIAL, PURPOSE, CD_PHA_MATERIAL, CONTENT, CONTAINER_ID, AI_FACTOR, PHA_MATERIAL_STATUS, C
MG_SPEC_APP, PROD_LEVEL, PACKAGE_SIZE, PRODUCT_ID FROM RCGC.PHA_V_COMPAS_MATERIAL WHERE (MAT_ID = '10021500150000000997'
[TopLink Fine]: 2007.01.19 02:56:48.468--ServerSession(17712783)--Connection(723185)--Thread(Thread[http-8080-Processor2
3,5,main])--SELECT PRODUCT_ID, PROD_GRP_ID, APPL_FORM_NAME, PRODUCT_NAME, GALENIC_FORM_NAME, APPL_FORM_ID, PHA_PRODUCT_S
TATUS, PHA_PRODUCT_LCOMMENT, GALENIC_FORM_ID, LU_PHA_PRODUCT, INN, LDT_PHA_PRODUCT FROM RCGC.PHA_V_COMPAS_PRODUCT WHERE
(PRODUCT_ID = 'COC003')
[TopLink Fine]: 2007.01.19 02:56:48.568--ServerSession(17712783)--Connection(32404901)--Thread(Thread[http-8080-Processo
r23,5,main])--SELECT APPL_CGP_MATLOC, CHANGE_REQ_MATLOC, CD_PHA_MAT_LOC, LCOMP, LOC_MAT_NAME, APPL_GDM_MATLOC, LOC_MAT_N
AME_SHORT, APPL_PDW_MATLOC, PHA_MAT_LOC_LCOMMENT, APPL_TP_MATLOC, DIVISION, APPL_WRS_MATLOC, ARTICLE_ID_MDA, LU_PHA_MAT_
LOC, LOC_MAT_NAME_OLD, LDT_PHA_MAT_LOC, PHA_MAT_LOC_STATUS, CU_PHA_MAT_LOC, MAT_LOC_ID, RCOMP, MAT_ID FROM RCGC.PHA_V_CO
MPAS_MAT_MATLOC WHERE (MAT_ID = '10021500150000000997')
[TopLink Warning]: 2007.01.19 02:56:48.638--UnitOfWork(4469532)--Thread(Thread[http-8080-Processor23,5,main])--Exception
[TOPLINK-6132] (Oracle TopLink Essentials - 9.1 (Build b22)): oracle.toplink.essentials.exceptions.QueryException
Exception Description: Query argument ######' not found in list of parameters provided during query execution.
Query: ReadAllQuery(de.merck.compas.material.SimilarLocalMaterialListItemBV)
Local Exception Stack:
Exception [TOPLINK-6132] (Oracle TopLink Essentials - 9.1 (Build b22)): oracle.toplink.essentials.exceptions.QueryExcept
ion
Exception Description: Query argument ######' not found in list of parameters provided during query execution.
Query: ReadAllQuery(de.merck.compas.material.SimilarLocalMaterialListItemBV)
at oracle.toplink.essentials.exceptions.QueryException.namedArgumentNotFoundInQueryParameters(QueryException.jav
a:206)
at oracle.toplink.essentials.internal.databaseaccess.DatasourceCall.getValueForInParameter(DatasourceCall.java:6
86)
at oracle.toplink.essentials.internal.databaseaccess.DatasourceCall.getValueForInOutParameter(DatasourceCall.jav
a:704)
at oracle.toplink.essentials.internal.databaseaccess.DatasourceCall.translateQueryString(DatasourceCall.java:630
at oracle.toplink.essentials.internal.databaseaccess.DatabaseCall.translate(DatabaseCall.java:850)
at oracle.toplink.essentials.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQuer
yMechanism.java:212)
at oracle.toplink.essentials.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQuer
yMechanism.java:199)
at oracle.toplink.essentials.internal.queryframework.DatasourceCallQueryMechanism.executeSelectCall(DatasourceCa
llQueryMechanism.java:270)
at oracle.toplink.essentials.internal.queryframework.DatasourceCallQueryMechanism.selectAllRows(DatasourceCallQu
eryMechanism.java:600)
at oracle.toplink.essentials.queryframework.ReadAllQuery.executeObjectLevelReadQuery(ReadAllQuery.java:302)
at oracle.toplink.essentials.queryframework.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:
709)
at oracle.toplink.essentials.queryframework.DatabaseQuery.execute(DatabaseQuery.java:609)
at oracle.toplink.essentials.queryframework.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:677)
at oracle.toplink.essentials.queryframework.ObjectLevelReadQuery.executeInUnitOfWork(ObjectLevelReadQuery.java:7
31)
at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2218)
at oracle.toplink.essentials.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:937)
at oracle.toplink.essentials.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:909)
at oracle.toplink.essentials.internal.ejb.cmp3.base.EJBQueryImpl.executeReadQuery(EJBQueryImpl.java:346)
at oracle.toplink.essentials.internal.ejb.cmp3.base.EJBQueryImpl.getResultList(EJBQueryImpl.java:447)
at de.merck.compas.material.SimilarLocalMaterialListItemBC.selectList(SimilarLocalMaterialListItemBC.java:40)
at de.merck.compas.material.SimilarLocalMaterialListItemBC.selectSimilar(SimilarLocalMaterialListItemBC.java:53)
at de.merck.compas.material.MaterialMaintainFS.init(MaterialMaintainFS.java:158)
at de.merck.compas.material.MaterialListSV.startMaterialMaintain(MaterialListSV.java:186)
at de.merck.compas.material.MaterialListSV.processPage(MaterialListSV.java:97)
at de.merck.jsfw.servletFramework.AbstractServlet.processPage(AbstractServlet.java:141)
at de.merck.jsfw.servletFramework.ControllerServlet.processLastPage(ControllerServlet.java:240)
at de.merck.jsfw.servletFramework.ControllerServlet.processRequest(ControllerServlet.java:206)
at de.merck.jsfw.servletFramework.ControllerServlet.doGet(ControllerServlet.java:181)
at de.merck.jsfw.servletFramework.ControllerServlet.doPost(ControllerServlet.java:191)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at de.merck.comp.ntml.NTLMFilter.negotiate(NTLMFilter.java:384)
at de.merck.comp.ntml.NTLMFilter.doFilter(NTLMFilter.java:165)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java
:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
The Toplink manifest file with version number:
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.5
Created-By: 1.5.0_09-b03 (Sun Microsystems Inc.)
Specification-Title: Java Persistence API
Specification-Vendor: Sun Microsystems, Inc., Oracle Corp.
Specification-Version: 1.0
Implementation-Title: TopLink Essentials
Implementation-Vendor: Sun Microsystems, Inc., Oracle Corp.
Implementation-Version: 9.1 build: b22
Thanks again for your help!

Named Parameters in Queries - the spec vs the Java EE 5 Tutorial

Hi,
I've been studying the topic about the named parameters in JPA and found one inconsistency between the spec and the Java EE 5 Tutorial. Could anyone lend me a helping hand understanding it?
The Java Persistence API spec (ejb-3_0-fr-spec-persistence.pdf) 3.6.3 "Named Parameters" at page 69 reads:
The use of named parameters applies to the Java Persistence query language, and is not defined for native queries.
whereas the Java EE 5 Tutorial in the section Named Parameters in Queries (http://java.sun.com/javaee/5/docs/tutorial/doc/PersistenceIntro3.html#wp81563) of The EntityManager reads:
Named parameters are case-sensitive, and may be used by both dynamic and static queries.
I think that the reality is that every JPA provider supports named parameters in dynamic and static queries, but it's not fully supported by the spec (yet not forbidden).
Jacek
Jacek Laskowski
http://www.jaceklaskowski.pl

Hi Jacek,
These are not conflicting statements. Named parameters apply to the Java Persistence
Query language only, not to native queries. There are two ways to specifiy
Java Persistence Query Language queries : dynamically and statically. You can
either pre-define the query string using @NamedQuery
static :
@NamedQuery(name="findPersonByName",
query="SELECT OBJECT(p) FROM Person p WHERE p.name LIKE :pName")
OR, pass the query string in at runtime using EntityManger.createQuery
dynamic :
em.createQuery("SELECT OBJECT(p) FROM Person p WHERE p.name LIKE :pName")
The dynamic approach allows you to construct portions of the query string at runtime.
My example doesn't do that but the point is that use of the createQuery()
API is considered the dynamic approach.
The crux of the Java EE 5 Tutorial statement you referenced is that named parameters apply to
both the static and dynamic use of Java Persistence Query Language queries.
--ken

Named parameters in Native SQL

A little background first:
Our website uses Hibernate as it's JPA provider, but we've run into several issues with it, one of which they actively refuse to fix out of pure arrogance, even when we gave them a good patch for it. The other one is a performance issue that can be greatly improved by passing arrays as parameters, which I've read rumours is supported in EclipseLink. I first tried implementing a Hibernate UserType as they've specified and it turns out they never read them into the Map that looks-up parameter types during binding, even though it's loaded from their hibernate.cfg.xml. In other words, they're only pretending to support custom user types, but unless you're writing-out the full manual loading of their configuration, there's no way to do it.
After a day of trying to fix all the relation annotations that EclipseLink finds unacceptable in our project (which only uses native SQL and EntityManager.find for selects) I finally got it running and came to discover you don't support named parameters in native SQL. That was really disappointing, because a few months ago we migrated all our queries to named parameters, because positioning ones were too difficult to track and caused more bugs when we had to add more criterias.
My questions are these:
Are named parameters for native SQL not supported by JPA specifications or because they are considered low priority?
Would you accept a patch that supports them?
Can we really use arrays and/or lists as parameters in queries like this "SELECT * FROM some_table WHERE my_column_a IN ? AND my_column_b NOT IN ?"
If yes to above, would it still work if the first one is an array of integers and the second is an array of strings?
Would it work if it's in native SQL and the column types cannot be resolved due to query complexity?

A little background first:
Our website uses Hibernate as it's JPA provider, but we've run into several issues with it, one of which they actively refuse to fix out of pure arrogance, even when we gave them a good patch for it. The other one is a performance issue that can be greatly improved by passing arrays as parameters, which I've read rumours is supported in EclipseLink. I first tried implementing a Hibernate UserType as they've specified and it turns out they never read them into the Map that looks-up parameter types during binding, even though it's loaded from their hibernate.cfg.xml. In other words, they're only pretending to support custom user types, but unless you're writing-out the full manual loading of their configuration, there's no way to do it.
After a day of trying to fix all the relation annotations that EclipseLink finds unacceptable in our project (which only uses native SQL and EntityManager.find for selects) I finally got it running and came to discover you don't support named parameters in native SQL. That was really disappointing, because a few months ago we migrated all our queries to named parameters, because positioning ones were too difficult to track and caused more bugs when we had to add more criterias.
My questions are these:
Are named parameters for native SQL not supported by JPA specifications or because they are considered low priority?
Would you accept a patch that supports them?
Can we really use arrays and/or lists as parameters in queries like this "SELECT * FROM some_table WHERE my_column_a IN ? AND my_column_b NOT IN ?"
If yes to above, would it still work if the first one is an array of integers and the second is an array of strings?
Would it work if it's in native SQL and the column types cannot be resolved due to query complexity?

Native TopLink named query with named parameters

Hello,
Defining my metadata in native TopLink xml and using the native TopLink's Session interface I can access and successfully execute a named query using positional parameters (parameters passed to match the ?1 ?2 etc). I used for this the Session.executeQuery(String, Class, List) method e.g.
select p from Person p where p.name = ?1
Now, how can I get the same Session to execute named queries using named parameters? None of the Session.executeQuery methods seem suitable ... Am I missing anything here? e.g.
select p from Person p where p.age = :age
I can't find in Session http://www.oracle.com/technology/products/ias/toplink/doc/1013/main/b13698/oracle/toplink/sessions/Session.html a good match for this use-case. I would expect something like:
Session.executeQuery(String queryName, Class target, List argNames, List argValues)
or
Session.executeQuery(String queryName, Class target, Map argsKeyedByName)
but can't find any good match, can anyone please enlighten me?
Thanks in advance,
Best regards,
Giovanni

Hello Chris,
Many thanks for your response. I am sorry if I did not explain my problem properly.
Suppose I already defined a named query in the metadata XXXProject.xml using the <opm:querying ... this JPQL named query "customFinder" already exists and would look something like:
select p from Person p where p.firstname=:firstname and p.lastname=:lastname and p.birthdate=:birthdate
now say you want to execute this query from the Session:
Vector args = new Vector();
// how do you know the order? you shouldn't know the order!
// you know only the parameter names and that's what I mean
// about named parameters
// This args setup is wrong ... I need a way to specify to which
// parameter name each argument corresponds to. In other words
// if the named query where criteria order of parameters is modified
// perhaps because of pruning composite keys etc you won't break the
// existing code ...
args.add(new Date());
args.add("Azua");
args.add("Giovanni");
Session session = ...
session.executeQuery("customFinder", Person.class, args);
JPA supports both type of queries positional parameters and named parameters. Your explanation above is only for the first, my question refers to the later.
I have not yet found the api for this ... though I am investigating along the lines of:
Query query = session.getQuery("customFinder");
and then try to assign the arguments in the same order that the parameters are defined in query or?
Thanks in advance,
Best regards,
Giovanni
Edited by: bravegag on 29.05.2009 08:06

Using named parameters with an sql UPDATE statement

I am trying to write a simple? application on my Windows 7 PC using HTML, Javascript and Sqlite. I have created a database with a 3 row table and pre-populated it with data. I have written an HTML data entry form for modifying the data and am able to open the database and populate the form. I am having trouble with my UPDATE function. The current version of the function will saves the entry in the last row of the HTML table into the first two rows of the Sqlite data table -- but I'm so worn out on this that I can't tell if it is accidental or the clue I need to fix it.
This is the full contents of the function . . .
     updateData = new air.SQLStatement();
     updateData.sqlConnection = conn;
     updateData.text = "UPDATE tablename SET Gsts = "Gsts, Gwid = :Gwid, GTitle = :GTitle WHERE GId = ":GId;
          var x = document.getElementsById("formname");
          for (var i = 1, row, row = x.rows[i]; i++) {
               updateData.parameters[":GId"] = 1;
               for (var j = 0, col; col=row.cells[j]; j++) {
                    switch(j) {
                         case 0: updateData.parameters[":GTitle"] = col.firstChild.value; break;
                         case 1: updateData.parameters[":Gsts"] = col.firstChild.value; break;
                         case 2: updateData.parameters[":Gwid"] = col.firstChild.value; break;
Note: When I inspect the contents of the col.firstChild.value cases, they show the proper data as entered in the form -- it just isn't being updated into the proper rows of the Sqlite table.
Am I using the named parameters correctly? I couldn't find much information on the proper use of parameters in an UPDATE statement.

Thank you for the notes. Yes, the misplaced quotes were typos. I'm handtyping a truncated version of the function so I don't put too much info in the post. And yes, i = 1 'cuz the first rows of the table are titles. So the current frustration is that I seem to be assigning all the right data to the right parameters but nothing is saving to the database.
I declare updateData as a variable at the top of the script file
Then I start a function for updating the data which establishes the sql connection as shown above.
The correctly typed.text statement is:
        updateData.text = "UPDATE tablename SET Gsts=:Gsts, Gwid=:Gwid, GTitle=:GTitle WHERE GId=:GId";
(The data I'm saving is entered in text boxes inside table cells.) And the current version of the loop is:
        myTable = document.getElementById("GaugeSts");
        myRows= myTable.rows;
          for(i=1, i<myRows.length, i++) {
               updateData.parameters[":GId"]=i;
               for(j=0; j<myRows(i).cells.length, j++) {
                    switch(y) {
                         case 0: updateData.parameters[":GTitle"]=myrows[i].cells[y].firstChild.value; break;
                         case 1: updateData.parameters[":Gsts"]=myrows[i].cells[y].firstChild.value; break;
                         case 2: updateData.parameters[":Gwid"]=myrows[i].cells[y].firstChild.value; break;
                         updateData.execute;
The whole thing runs without error and when I include the statements to check what's in myrows[i].cells[y].firstChild.value, I'm seeing that the correct data is being picked up for assignment to the parameters and the update. I haven't been able to double check that the contents of the parameters are actually taking the data 'cuz I don't know how to extract the data from the parameters. ( The only reference I've found so far has said that it is not possible. I'm still researching that one.) I've also tried moving the position of the updateData execution statement to several different locations in the loop andstill nothing updates.
I am using a combination of air.Introspector.Console.log to check the results of code and I'm using Firefox's SQlite manager to handle the database. The database is currently sitting on the Desktop to facilitate testing and I have successfully updated/changed data in this table through the SQLite Manager so I don't think I'm having permission errors and, see below, I have another function successfully saving data to another table.
I currently have another function that uses ? for the parametersin the .text of a INSERT/REPLACE statement and that one works fine. But, only one line of data is being saved so there is no loop involved. I tried changing the UPDATE statement in this function to the INSERT/REPLACE just to make something save back to the database but I can't make that one work either.I've a (And, I've tried so many things now, I don't even remember what actually saved something --albeit incorrectly --to the database in one of my previous iterations with the for loops.)
I'm currently poring through Sqlite and Javascript tomes to see if I can find what's missing but if anything else jumps out at you with the corrected code, I'd appreciate some ideas.
Jeane

Named Parameters in Functions: Possible?

I want to use named parameters to call PL/SQL functions using JDBC, as is best practice and necessary for default values to work. Unfortunatley all the examples I found are for procedures only. Using a positional registerOutParameter with named register / get methods on the CallableStatement does not work, obiviously.
Is there any proper way to use named parameters with functions ? Proper does not include writing wrapper procedures nor turning functions into procedures.

Hi Avi,
as far as I know the return value of a PL/SQL function does not have a name, as oposed to the parameters of a PL/SQL function, which must have a name. One could argue that the return value of a function is called the same as the function itself. I have tried that option but it does not work.
Unfortunatley the method OraclePreparedStatement.registerReturnParameter refers to something else than the return value of a PL/SQL function. Is it possible that the developers of the driver have forgotten something?

Named parameters in stored function

Hi,
I am trying to execute stored function from java in oracle . I am using Oracle 9.2.0.1.0 and the newest JDBC drivers, ie. for 10g which are compatible. I have flicked through JDBC Named Parameters example but it only addresses stored procedures.
The problem I have is that I do not know what name the return value of stored procedure has.
stored function parameter names:
1. ????
2. test1 Mode: IN
3. test2 Mode: IN
?=call test_function(?,?);
When I am trying to set values as indexes everything works perfect.
CallableStatement cs = .....
cs.registerOutParameter(1, Types.VARCHAR);
cs.setString(2, "a");
cs.setString(3, "b");
cs.execute();
String returnedValue = cs.getString(1);
However, when I am trying to use named parameters the code looks like this:
CallableStatement cs = .....
cs.registerOutParameter(1, TYPES.VARCHAR);
cs.setString("test1", "a");
cs.setString("test2", "b");
and the question is what is the name of return parameter.
I have tried to put the same name as the name of stored function but is reports error.
Instead I had to first getmetadata from oracle and in case of stored functions utilize it, unfortunatelly getting metadata has perfomance issues and I heard that oracle 10g is even slower in getting metadata.
If anyone knows the answer to my question, please answer.
Thank you in advance,
Mateusz Szczap
Java Programmer
NCDC
[email protected]
http://www.ncdc.pl

Hi,
I am trying to execute stored function from java in oracle . I am using Oracle 9.2.0.1.0 and the newest JDBC drivers, ie. for 10g which are compatible. I have flicked through JDBC Named Parameters example but it only addresses stored procedures.
The problem I have is that I do not know what name the return value of stored procedure has.
stored function parameter names:
1. ????
2. test1 Mode: IN
3. test2 Mode: IN
?=call test_function(?,?);
When I am trying to set values as indexes everything works perfect.
CallableStatement cs = .....
cs.registerOutParameter(1, Types.VARCHAR);
cs.setString(2, "a");
cs.setString(3, "b");
cs.execute();
String returnedValue = cs.getString(1);
However, when I am trying to use named parameters the code looks like this:
CallableStatement cs = .....
cs.registerOutParameter(1, TYPES.VARCHAR);
cs.setString("test1", "a");
cs.setString("test2", "b");
and the question is what is the name of return parameter.
I have tried to put the same name as the name of stored function but is reports error.
Instead I had to first getmetadata from oracle and in case of stored functions utilize it, unfortunatelly getting metadata has perfomance issues and I heard that oracle 10g is even slower in getting metadata.
If anyone knows the answer to my question, please answer.
Thank you in advance,
Mateusz Szczap
Java Programmer
NCDC
[email protected]
http://www.ncdc.pl

JavaDB or Toplink not recognizing named parameters?

Creating a query within a session bean but the named parameter is causing an exception. Using Derby with Toplink in the Sun App Server 9.0_01. Any ideas what the problem or solution is?
    public String getNumberOfInvoices(String supplierAccount) {
        String suppAcc = "";
        Query qry = em.createNativeQuery(
                "select count(d) from App.Documents as d " +
                "where d.PERSONALACCOUNT = :suppAcc;");
        qry.setParameter("suppAcc", supplierAccount);
        Long count = (Long) qry.getSingleResult();
        return Long.toString(count);
[#|2007-09-22T23:41:09.271+0100|WARNING|sun-appserver-pe9.0|oracle.toplink.essentials.file:/C:/Sun/SDK/domains/domain1/applications/j2ee-apps/Accounting/Accounting-ejb_jar/-Accounting-ejbPU|_ThreadID=16;_ThreadName=httpWorkerThread-8080-1;_RequestID=4ffb3c50-34f3-42cf-a00b-26e93a0f8ed6;|
Local Exception Stack:
Exception [TOPLINK-4002] (Oracle TopLink Essentials - 2006.8 (Build 060830)): oracle.toplink.essentials.exceptions.DatabaseException
Internal Exception: org.apache.derby.client.am.SqlException: Syntax error: Encountered ":" at line 1, column 67.Error Code: -1
Call:select count(d) from App.Documents as d where d.PERSONALACCOUNT = :suppAcc;
Query:DataReadQuery()
     at oracle.toplink.essentials.exceptions.DatabaseException.sqlException(DatabaseException.java:303)
     at oracle.toplink.essentials.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:551)
     at oracle.toplink.essentials.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:437)
     at oracle.toplink.essentials.threetier.ServerSession.executeCall(ServerSession.java:465)
     at oracle.toplink.essentials.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:213)
     at oracle.toplink.essentials.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:199)

This seems to have resolved the problem to a degree. I am not sure why
numeric parameters are accepted but named one are not. I don't know. I can do named parameters with Hibernate. I don't know TopLink.
You understand that "named query" is different from "query with named parameters", right? You seem to want the latter, not the former. Maybe you're reading the wrong docs.
I have also
changed from count(d) to count(*). Is this because I am using EJB Query
Language but createNativeQuery is plain JDBC?
If you're counting all the rows in a table, it would be count(*). If you want to only count certain rows, it'd be a GROUP BY and HAVING.
Any way the error is now saying:-
Caused by: java.lang.ClassCastException: java.util.Vector cannot be cast
to java.lang.Long
This is pretty clear. You're assuming that the method returns a Long and it's telling you that it returns a Vector. It should only have size 1, and you should get the zeroth index value out of it.
%

Named Parameters in CallableStatement HELP!!!!!!!

Help please. Such syntax as "select * from table1 where t1_name like ?" and "CallableStatement.setString("name","%ALICE%")" throws an
java.lang.AbstractMethodError: oracle.jdbc.driver.OracleCallableStatement.setString(Ljava/lang/String;Ljava/lang/String;)
Why is it abstract??? Can anyone help to overcome it?

Alexander,
Have you seen the Named Parameters Sample?
Good Luck,
Avi.

PL/SQL named parameters

When editing a PL/SQL package I can type a package body name and "." and get a list of function/procedures to choose from. When I choose a function/procedure from the list I would like jdeveloper to dump out the function call complete with named parameters similar to the way it generates an anonymous block for you when you choose to run a function or procedure. How does one do this.
Thanks in advance.

Hi,
the best way is to check this feature being avaiable in SQL Developer because JDeveloper 11 will consume their code base for the integrated PSLQL development environment. Let me know if you can't find it in there and I'll fiel an enhancement request against SQL Developer
Frank

Only named ECParameters supported?

I'm having this SSLProtocolException while trying to connect to an OpenSSL server using JDK1.6. The same code is working with JDK 1.5. What does this named ECParameter mean? My OpenSSL server is using NID_sect163r2 curve.
Here is part of my code to generate SSLSocket:
SSLContext sslCtx = SSLContext.getInstance("TLS");
MyTrustManager tm[] = new MyTrustManager[1];
tm[0] = new MyTrustManager();
sslCtx.init(null, tm, null);
SSLSocketFactory sf = sslCtx.getSocketFactory();
SSLSocket socket = (SSLSocket)sf.createSocket(server, port);
And the whole SSL communication message is:
SSLContext class: class javax.net.ssl.SSLContext
Protocol: TLS
Provider: SunJSSE version 1.6
trigger seeding of SecureRandom
done seeding SecureRandom
%% No cached client session
*** ClientHello, TLSv1
RandomCookie: GMT: 1176390882 bytes = { 63, 105, 168, 46, 149, 87, 91, 38, 105, 23, 3, 24, 226, 70, 43, 244, 178, 136, 110, 170, 87, 48, 85, 69, 126, 210, 19, 45 }
Session ID: {}
Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
Compression Methods: { 0 }
main, WRITE: TLSv1 Handshake, length = 73
main, WRITE: SSLv2 client hello message, length = 98
main, READ: TLSv1 Handshake, length = 74
*** ServerHello, TLSv1
RandomCookie: GMT: 1176390881 bytes = { 139, 43, 74, 230, 203, 174, 215, 84, 222, 72, 118, 176, 186, 121, 11, 238, 27, 118, 98, 13, 102, 187, 18, 232, 68, 153, 5, 142 }
Session ID: {222, 156, 122, 253, 124, 124, 49, 111, 255, 47, 109, 0, 109, 189, 129, 17, 49, 210, 216, 90, 120, 214, 33, 116, 99, 88, 17, 232, 97, 12, 112, 209}
Cipher Suite: SSL_RSA_WITH_3DES_EDE_CBC_SHA
Compression Method: 0
%% Created: [Session-1, SSL_RSA_WITH_3DES_EDE_CBC_SHA]
** SSL_RSA_WITH_3DES_EDE_CBC_SHA
main, READ: TLSv1 Handshake, length = 805
main, handling exception: javax.net.ssl.SSLProtocolException: java.io.IOException: Only named ECParameters supported
main, SEND TLSv1 ALERT: fatal, description = unexpected_message
main, WRITE: TLSv1 Alert, length = 2
main, called closeSocket()
Thanks in advance,

This looks like Sun's Keystore implementation cannot load a ECDSA key if it was created in some particular way:
import java.io.FileInputStream;
import java.security.KeyStore;
public class KeyLoader {
      // For some reason JRE 1.6 cannot recover the key
     public static void main(String args[]) throws Exception {
          FileInputStream fin = new FileInputStream("mykeystore.jks");
          KeyStore ks = KeyStore.getInstance("JKS");
          ks.load(fin, "password".toCharArray());
          ks.getKey("tcsign", "password".toCharArray());
}Exception in thread "main" java.security.UnrecoverableKeyException: Only named ECParameters supported
     at sun.security.provider.KeyProtector.recover(KeyProtector.java:321)
     at sun.security.provider.JavaKeyStore.engineGetKey(JavaKeyStore.java:121)
     at sun.security.provider.JavaKeyStore$JKS.engineGetKey(JavaKeyStore.java:38)
     at java.security.KeyStore.getKey(KeyStore.java:763)
     at KeyLoader.main(KeyLoader.java:12)

Call procedure with named parameters

Call procedure with positional parameters works, but with named parameters gives an ORA-907.
This post seems similar: Re: Error with report - pkg and bind var
Run as a script:
set echo on
call dbms_stats.delete_table_stats ('ZZZMIG', 'CHAINED_ROWS', cascade_columns=>true, no_invalidate=>false);
call dbms_stats.delete_table_stats ('ZZZMIG', 'CHAINED_ROWS');
begin dbms_stats.delete_table_stats ('ZZZMIG', 'CHAINED_ROWS', cascade_columns=>true, no_invalidate=>false); end;
gives:
set echo on
call dbms_stats.delete_table_stats ('ZZZMIG', 'CHAINED_ROWS', cascade_columns=>true, no_invalidate=>false)
Error starting at line 2 in command:
call dbms_stats.delete_table_stats ('ZZZMIG', 'CHAINED_ROWS', cascade_columns=>true, no_invalidate=>false)
Error report:
SQL Error: ORA-00907: missing right parenthesis
00907. 00000 - "missing right parenthesis"
*Cause:
*Action:
call dbms_stats.delete_table_stats ('ZZZMIG', 'CHAINED_ROWS')
call dbms_stats.delete_table_stats succeeded.
begin dbms_stats.delete_table_stats ('ZZZMIG', 'CHAINED_ROWS', cascade_columns=>true, no_invalidate=>false); end;
anonymous block completed
I like the idea of using call, because the procedure name appears in the feedback - useful in longer scripts.
I'm using SQL Developer Version 1.5.1 Build MAIN-5440
on Windows XP SP3
with database EE 10.2.0.3

CALL is a SQL command which executes a routine
(procedure/function)
http://download-uk.oracle.com/docs/cd/B19306_01/server
.102/b14200/statements_4008.htm
whereas EXECUTE is a SQL*Plus command which executes
a single PL/SQL statement
http://download-uk.oracle.com/docs/cd/B19306_01/server
.102/b14357/ch12022.htm#i2697931
Message was edited by:
Jens PetersenThank you very much, esp. for the links!

When will external table field_list in access parameters support varchar2?

Hello all,
Currently I'm working on a CSV error check/upload/download utility (in pl/sql) using external tables. However, within the access parameters section, when I tried to use varchar2 in the field list to map to data fields in csv, oracle (10g) complaint that I cannot use varchar2.
Therefore I am forced to use char (Feuerstein explictly told us not to use varchar in PL/SQL Programming) to map to the data. However, since some fields in the DB are actually varchar2(4000), and the max length supported by char type in sqlplus is 2000, I'm creating this ridiculous machine:
- data in csv can hava a maxlength of 4000 characters
- staging table to which csv data will go to is varchar2(4000)
- field list in external table creates a bottleneck of char(2000)
As a result, I'm betting on the user never will enter any string longer than 2000 character into csv, even though the DB supports it. However, this would be way too fragile to go into production.
Does anybody know if Oracle 11g external tables support varchar2, or are there any workarounds (besides using sqlldr)? Many thanks.

Hi, my external table spec is something like this:
create table x_table (
field1           varchar2(4000),
field2           varchar2(4000),
field3           varchar2(4000))
organization external (type oracle_loader default directory ext_tab_dir
          access parameters (
          records delimited by newline
          badfile ext_tab_dir:'importcsv.bad'
          discardfile ext_tab_dir:'discarded.txt'
          logfile ext_tab_dir:'importcsv.log'
          skip 1
          fields terminated by '|' lrtrim
          missing field values are null
          reject rows with all null fields
          (field1 char(2000),
          field2           char(2000),
          field3           char(2000))
          location ('test_xtable.csv'))
          reject limit unlimited;
The portion below the phrase "reject rows with all null fields" is what I meant by "field mapping", since I use it to match the csv structure. The order within the fields specification above the "organization external" can be rearranged any way I like, as long as the field name has a matching one in the "field mapping". Right now, I can only use char(2000) or varchar(2000) in the "field mapping" area, but not varchar2. Any ideas?

Parameterized support for multiple database instances in CR 4 Eclipse

Issue with Database Schemas and Crystal Reports
When building a report with Crystal Reports, the user is required to enter database connectivity information. This database information allows the user to select which tables the information for the report will come from. When choosing the tables, the user must navigate through the available database schemas in the database connection to each table that is required. The database structure is described below:
Database Connector 1
Schema1
Schema2
Table1
Table2
Table3
Schema3
After the user has selected the appropriate tables, they are allowed to begin building the report. The user puts the necessary table fields onto the report. Crystal Reports uses only the required fields on the report to build a query to the database for retrieving the data. Thus, the fewer the fields on the report, the less information required. A single query is built by Crystal Reports to get all the data from the database. This query can be viewed from within the Crystal Reports application, but it cannot be changed by the user.
When viewing the query generated by Crystal Reports, you will notice that the tables will have the schema name attached to them. This is done as part of the fully qualified name of the table.
Processing a Crystal Reports report in a batch environment requires that the database connector that is stored inside the report be changed. This change is necessary due to the setup of our system. The name of the database server, the database username and the database password are different in the different execution environments. Our current implementation is to programmatically change these values before running the report.
The issue arises in that changing the database connector does not change the schema of the tables used in the query. The schema information in the query is hardcoded. Thus, when moving the reports from one environment to another, the original schema used is being propogated to the new environment, where the original schema is not appropriate.
Changing the database connector will, however, change the schema of the tables used in the field selector. Any field that is used from the field selector on the report or in formulas will change appropriately. But the fields used to create the initial query will not change.
The results of the schema not being changed appropriately in the query is when the report is attempting to populate with the Java environment, an exception is thrown and processing is terminated. When the exception is thrown, the entire process of populating the report is terminated.
Anyone know a solution to this?
Erik Bleifield

Well, CSV would not be a preferred option.
We need to get the output to a report archive that only supports ascii text. We are hoping to preserve the output formatting of columns, etc. CSV would not preserve the formatting.
We are currently looking at outputting to PDF and then running a 3rd party product to convert from PDF to text. This leads to a good amount of formatting issues as well.
Why would exporting to text not be supported in Java? Where one can execute this manually in CR 2008 for Windows.
I wonder if this is intentional by product management choice - or a defect?
Thanks for further consideration.
Erik

Named parameters support

Similar Messages

Maybe you are looking for