Try/catch variable scope

[Alessandro Camel]

Hello all,
I have a problem with a variable scope!

The variable is declared into a try/catch block, but later I need it in order to call a method, but I can't see it!
I am talking about the variable connection :

 try {
	Connection connection = null;
	// Load the JDBC driver
	String driverName = "org.gjt.mm.mysql.Driver"; // MySQL MM JDBC driver
	Class.forName(driverName);
			    
	// Create a connection to the database
	connection = DriverManager.getConnection(url, username, password);
}
..
..
..
InsertRigaInDB(connection,Data,Why,Import,Note);

What is the correct way to go round this ?
Thanks!

[bhanu chowdary]

Declare the variable connection before the try block. This should your problem. With your code the scope of the variable is confined to the try block

[Bear Bibeault]

Why would you need it outside of the try block? If the code fails, is it meaningful to try and use a variable that may not be valid?

Perhaps the structure of your code is not quite right?

[Suhas Mandrawadkar]

Declare connection outside try block.

Connection connection;
try{
}

[Bear Bibeault]

Suhas Mandrawadkar wrote:Declare connection outside try block.

Which will cause the error to go away, but will it be correct? Is the structure of the code improved by this approach?

[Alessandro Camel]

Bear Bibeault wrote:Why would you need it outside of the try block? If the code fails, is it meaningful to try and use a variable that may not be valid?

Perhaps the structure of your code is not quite right?

I am quite sure that the structure is bad
I am not quite confident with the OOP.

My exercize is:
Read line by line a csv file
Insert every line inside a mysql table

My idea is using a method to group the insert task code to avoid all the sql lines inside the while-read-file block.

[bhanu chowdary]

Bear Bibeault wrote:If the code fails, is it meaningful to try and use a variable that may not be valid?

But Bear, in case if the code fails we may not be doing what we do when there is a successful connection created

[Bear Bibeault]

bhanu chowdary wrote:But Bear, in case if the code fails we may not be doing what we do when there is a successful connection created

I'm not sure what you are trying to say. But my point is that if the purpose of the try block is to make sure that a good connection is established, why would you reference it outside of the try block where you do not know if it has been successful or not?