This discussion is archived
1 2 Previous Next 16 Replies Latest reply: Dec 18, 2012 2:43 PM by dsurber Go to original post RSS
  • 15. Re: Difference between setString and setStringAtName
    HJHorst Explorer
    Currently Being Moderated
    Thanks for your elaborate reply.

    I ran into this when using ADF Business Components where you can select a binding style.
    One of these is Oracle Positional. I think this is much used in EBS.

    It is documented in JDeveloper Help:

    Oracle Positional
    This style represents parameters as colons followed by numbers, as in the following code fragment:

    WHERE bar = :1 AND foo = :2

    In this style, the numbers are just for easier readability: Parameters are passed into the view object in the order in which the numbers occur. The above fragment, for example, is equivalent to

    WHERE bar = :70 AND foo = :3

  • 16. Re: Difference between setString and setStringAtName
    dsurber Explorer
    Currently Being Moderated
    The Oracle JDBC Development Team always recommends using standard JDBC whenever possible. We optimize the code to support the standard methods and classes. Don't use Oracle proprietary extensions unless necessary. In this case, use standard '?' parameters instead of proprietary ':foo' parameters. I can't think of a case where you would actually want to use ':foo' and setFooAtName.

1 2 Previous Next


  • Correct Answers - 10 points
  • Helpful Answers - 5 points