I’m new to asp.net so this might be really basic question, but i cant figure it out.
I found a bit of code on the internet, that connects to database. And i created a namespace and some classes to use the same code in different projects.
The code and my class is the following:
namespace databaseFunctions
{
public class databaseConnection
{
private static string databaseConnectionString()
{
return "DRIVER={MySQL ODBC 5.1 Driver}; ........";
}
public static DataTable getFromDatabase(string SQL)
{
DataTable rt = new DataTable();
DataSet ds = new DataSet();
OdbcDataAdapter da = new OdbcDataAdapter();
OdbcConnection con = new OdbcConnection(databaseConnectionString());
OdbcCommand cmd = new OdbcCommand(SQL, con);
da.SelectCommand = cmd;
da.Fill(ds);
try
{
rt = ds.Tables[0];
}
catch
{
rt = null;
}
return rt;
}
public static Boolean insertIntoDatabase(string SQL)
{
OdbcDataAdapter da = new OdbcDataAdapter();
OdbcConnection con = new OdbcConnection(databaseConnectionString());
OdbcCommand cmd = new OdbcCommand(SQL, con);
con.Open();
try
{
cmd.ExecuteNonQuery();
return true;
}
catch
{
return false;
}
}
}
There is no problem getting data from database, or insert data into some database.
But. when i try to get the last_insert_id() from the mysql database. i only get a zero.
This is why i think that this piece of code I’ve created and copied from internet, creates a new connection for every time i call the “getFromDatabase(SQL)”
Is there anyone that could help me with fixing this class getFromDatabase() to keep the databaseconnection alive until i tell the program to abandon the connection?
I guess it is the “new OdbcConnection” that should be changed? Is it possible to check if there already is a connection alive?
I’ve done this hundreds of times in classic asp, but now, with classes and stuff. I’m totally lost.
The problem you face is that you’ve coded yourself into a “new connection per action” corner. What you really want to aim for,and is considered best practice, is “new connection per batch of actions”.
What I recommend in this case is to open connection when required, and close when disposed. What we’ll do is move the odbc adapters to a larger scoped variable so that it can be accessed within the class.
Now the next time you use your class do something like
At the end of that code block, because it is IDisposeable, it will close that connection for you in the dispose method.
Things I changed:
Edits: