PreparedStatement/Parameter Error

[Draug]

Greetings,
The code below creates a runtime Null Pointer Exception.

Can anyone tell me why? If I replace the ':well' and ':attach' with '?', everything works fine, but I dont think I should have to do that.

////////////////////////////////////////////////////////////
queryString = "Select Path From LW_ATTACHMENT Where Well_Id=:well and Attachment_Id=:attach";

ps = conn.prepareStatement(queryString);
ps.setString(1, "1"
ps.setString(2, "27038"
rset = ps.executeQuery();
////////////////////////////////////////////////////////////

Thanks alot people

 

[DixieFlatline]

you do know that the "?" is required... that's the syntax... check out the doc on java.sql package

the method is implemented to look for '?' char, how can you just change the pre-condition of the method.

 

[Draug]

Well, someone told me that it was not required, and that naming a parameter with a colon followed by a name would work...guess it wont.

Thanks

 

[DixieFlatline]

maybe it would, but from what i have seen and used to date, prepared statements are pretty iffy... it works if it is used perfectly... otherwise it dies pretty badly... it maybe easier to use resource bundler and get your sql pieces and build up the sql str yourself. a better practice yet is to use store procs.

good luck,

dix

 

[crufty]

Using the java.sql.* package, you have to create prepared statements with the '?' character

From SQL*Plus (Oracle), you create bind variables by using the :variable notation.

 

[daniel135]

I use java.sql and have no problem using ':id' instead of '?'. Are we using different releases or something?

Regardless, you should do what works for you.

 

[Draug]

Daniel135,

What release are you using? I am using JDK 1.3, which packaged with JBuilder4.

For a variety of longwinded reasons, it would be much better if I could use ':id' instead of '?'.

Draug