Problem updating mySQL database

Question

I am trying to update some data in one of my tables called topic in my SQL database. I have the follwing code which gets data from a bean and updates it in the database but it does not seem to work. I do not get an exception but it will not update the record even though the bean displays the correct information about the update it does not seem to update the database, Does anyone have any idea where i am going wrong?
String updateTopic__topicID = null;
if (request.getParameter("topicID") != null) {
    updateTopic__topicID = (String)request.getParameter("topicID");
String insertTopic__username = null;
if (session.getValue("MM_Username") != null) {
    insertTopic__username = (String)session.getValue("MM_Username");
Driver DriverupdateTopic   = (Driver)Class.forName(MM_connQuestion_DRIVER).newInstance();
Connection ConnupdateTopic = DriverManager.getConnection(MM_connQuestion_STRING, MM_connQuestion_USERNAME,
                                                         MM_connQuestion_PASSWORD);
PreparedStatement updateTopic =
                      ConnupdateTopic.prepareStatement("UPDATE Question.topic  SET Topic_Name = '" + topicData.topicName
                                                           + "', Description = '" + topicData.topicDescription
                                                           + "'  WHERE Topic_ID = '" + updateTopic__topicID + "' ");
updateTopic.executeUpdate();

Answer 1

I tried to check it and it did not update any records
cos i got this.
Records updated: 0
The WHERE claus does match my database record because
it is called Topic_ID which is the primary key for
that table. could it be something that is wrong with
my database?
Sir,
That is unlikely.
What is more likely is that something is wrong with your code somewhere.
I am somewhat suspicious of the STRING nature of Topic_ID. That is an auto_incrementing field I think? If so try setInt or setLong.
And to answer the followup question to that.
int anintvalue = Integer.parseInt(astringvalue);The other possibility is that in your form or whatever the value of the Topic_ID is getting mucked up. I would check to make sure you have the value you think.
Finally always make sure you are talking to the database you think you are. I realize this seems stupid but in testing environments these things do happen more often then one might suppose.
Sincerely,
Slappy