Using setObject() instead of all data types in ojdbc

Question

can I use setObject() method of PreparedStatement for all datatypes(like string, int, double..) for Oracle database and in its OJDBC?

Possible duplicate is this :

setObject() method of PreparedStatement

But I want to know about using it for Oracle database and OJDBC. What are possible problems?

jny · Accepted Answer · 2013-12-03 16:21:35Z

2

The possible problems are:

You are delaying type validation till the application execution and don't take advantage of type safety. So you'll have errors during execution which could be easily caught at compilation time.
You are loosing control of how types are inferred which might lead to weird formatting in some cases

My advise is to use setObject only if absolutely necessary.

answered Dec 3, 2013 at 16:21

jny

8,0873 gold badges39 silver badges56 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Keppil · Accepted Answer · 2013-12-03 16:25:27Z

1

One problem that I came across is the ambiguity that arises in case of null values. In my application, this led to problems for the database to cache queries properly. To avoid this I had to check if the value was null and use #setNull(index, class) in these cases.

For non-null values I haven't come across any problems.

answered Dec 3, 2013 at 16:25

Keppil

46.3k9 gold badges101 silver badges121 bronze badges

Collectives™ on Stack Overflow

Using setObject() instead of all data types in ojdbc

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related