Type mismatch: cannot convert from int to ResultSet

executeUpdate returns an int indicating how many rows were affected by the query. It does not return a resultset. So, on the line where you are carrying out an executeUpdate, you should not be expecting a ResultSet as the return value.

executeUpdate returns an int indicating how many rows were affected by the query. It does not return a resultset. So, on the line where you are carrying out an executeUpdate, you should not be expecting a ResultSet as the return value.

Hahah yeah i found that answer on another post but it didnt really help jsut cos im a java noob and couldnt think of any other way to fix the problem. Though for all of you who have a similar error i fixed it by doing this
[jsp]
Statement statement = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE,
ResultSet.CONCUR_UPDATABLE);
ResultSet rs = statement.executeQuery(" SELECT * FROM USERS");

rs.moveToInsertRow();
rs.updateString(1, username);
rs.updateString(2, password);
rs.updateString(3, usertype);
rs.updateString(4, email );
rs.updateString(5, title);
rs.updateString(6, firstname);
rs.updateString(7, lastname);
rs.updateString(8, phone);
rs.updateString(9, address);
rs.updateString(10, state);
rs.updateString(11, post);
rs.updateString(12, country);
rs.updateString(13, dob);
rs.updateString(14, credit);
rs.updateString(15, expiry);
rs.updateString(16, login_date);
rs.insertRow();
[/jsp]

and now it works beautifully! thanks for you help!
cheers.

And, yes it would have helped. Using an Updateable ResultSet was not the fix. There is no need to evaluate what is returned from an executeUpdate. Using an updateable resultset in this situation is complete overkill. Removing the return help would have fixed the problem posted. Any additional error was probably in the formulation of your query. Had you made the change requested, then posted again with the next error, we would have helped you get your query right. Which probably would have entailed telling you to use a PreparedStatement which would be used almost exactly like an updateable resultset without having to fetch anything from the database. You will probably, as time goes on, find out that this portion of your application gets slower, and slower, and slower, since in order to update the record you are trying to update, you must first fetch all users out of the database which will use up time and resources (and as you get more users these things will not be trivial) that you don't need to use.

Oh i see, yeah thats a much better idea. I get what you mean by it gradually using up more an more time as the DB gets bigger and bigger, since its doing a select all first. The PreparedStatement works a treat. I am now trying to make it generate some kind of error unless all fields are entered this is what i have added
[jsp]
if(username == "" || password == ""|| usertype == ""|| email == ""|| title== ""|| firstname== ""
|| lastname== ""|| phone== ""|| address== ""|| state== ""|| post== ""|| country== ""|| dob== ""
|| credit== ""|| expiry== ""|| login_date== "")
{

out.println("<h1>Please enter all mandatory fields</h1>");
}
else
{
Statement statement = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE,
ResultSet.CONCUR_UPDATABLE);
ResultSet rs = statement.executeQuery(" SELECT * FROM USERS");

rs.moveToInsertRow();
rs.updateString(1, username);
rs.updateString(2, password);
rs.updateString(3, usertype);
rs.updateString(4, email );
rs.updateString(5, title);
rs.updateString(6, firstname);
rs.updateString(7, lastname);
rs.updateString(8, phone);
rs.updateString(9, address);
rs.updateString(10, state);
rs.updateString(11, post);
rs.updateString(12, country);
rs.updateString(13, dob);
rs.updateString(14, credit);
rs.updateString(15, expiry);
rs.updateString(16, login_date);
rs.insertRow();
}
}
[/jsp]

Though this seems to do absolutely nothing, it always has "please enter all fields" at the bottom of the form. Im sure im going about this all wrong, could you possilbly point me in the right direction?

Thanks a bundle.

You can't, generally, compare strings with == you should do it as follows:

if ((usermame == null) || (username.length() == 0)) {
}

or

if ((usermame == null) || (username.equals(""))) {
}

Since getParameter can return a null value, and I don't believe that

"".equals(username)

will return true if username is null, a check for the null string is needed as well as the check for a nonempty value.

i have a suggestion a shorter line for the null hope it helps

Code:
if (username.length() <= -1) {
}

i suggest you create a javascript for validation. so that required fields all have a value. and to make sure that they are not null ^_^

Ken - Ken

javascript for validation and not null would be fine, except for those people that disable javascript in their browsers, and them doing that should not affect the ability of your jsp to deal with their input and in this case it would as a nullpointer exception would be thrown.

JavaScript is nice to use. You can accomplish a lot with it, but you should never depend on client side verification.

how to solved the error Type mismatch: cannot convert from Set<NeighbourConfiguration> to NeighbourConfiguration

NeighbourConfiguration NeighbourConfiguration = EnodeBConfigurationMgmt.getNeighbourConfiguration(nibEnbConfigId);