"System.out.println" has nothing to do with the DB - it serves as a debugging aid. The point Edwin was trying to make is that you should check what the actual query looks like that gets sent to the DB.
As a side note, it is much better to use a PreparedStatement than to construct the query on the fly using string concatenation. Amongst other benefits, it makes sure that the code isn't susceptible to SQL injection attacks.
Joined: Apr 19, 2008
The examples on prepared statements are not that complete.
Is this good? The print statement for the query gives me the following without a semicolon:
Thanks in advance,
Joined: Mar 22, 2005
What happens if you run that query directly against the DB? Are you getting results returned?
It was a matter of case. I changed the column to uppercase and it works. I did not realize SQL was case sensitive.
I also changed it to use Prepared Statement. Now somebody has adviced me to use Hibernate and Spring. So I have to research that. Sure I will be posting questions with that.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com