Here's my code for making an entry into the MySQL db using PDO.
$sql="INSERT INTO dictionary (entry, meaning) VALUES (:entry,:meaning)";
$prep=$db->prepare($sql);
$prep->bindParam(':entry',$entry);
$prep->bindParam(':meaning',$meaning);
try{
$result=$prep->execute();
}
catch(PDOException $e)
{
echo $e->getMessage();
}
But it's not inserting anything on the db. What could be the problem?
Well, it is useless to ask other people what is wrong with your code. You have to ask your server instead.
So, make sure your PDO throws exceptions on errors. To do so, add this line after connection code
$db->setAttribute( PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION );
Next, move try higher in the code
try{
$sql = "INSERT INTO dictionary (entry, meaning) VALUES (:entry,:meaning)";
$prep = $db->prepare($sql);
$prep->bindParam(':entry',$entry);
$prep->bindParam(':meaning',$meaning);
$result=$prep->execute();
} catch(PDOException $e) {
echo $e->getMessage();
}
and in case of any error you'll be notified of it.
Related
I try to run a cronjob to insert about 60000 rows into DB:
DB::beginTransaction();
try {
DB::table('pharmacies')->delete();
foreach(array_chunk($data, 50) as $piece) {
Pharmacy::insert($piece);
}
DB::commit();
\Log::debug("Save successfully");
} catch(\Exception $e) {
DB::rollback();
\Log::debug($e->getMessage());
}
}
The cronjob is working normally. I test for a few first times, it saves successfully. But then, It suddenly can't save and from this time the data can't save without any error.
I don't know why the data can't save but it doesn't catch exceptions to log the error message?
Any idea or suggestion for this case. Please help me. Thank you so much!
What is your CORN-JOB configuration? check /var/log/syslog for logs
I need to access to an online file and reading is content, but if for some reason the file isn't available due network/server problem ill use a local version stored on my server.
For doing that I've written this simple code:
$response = Http::timeout(2)->get('http.site/file.json');
And I add this for checking if all is ok:
if($response->successful()){
$list = $response->body();
} else {
$list = file_get_contents(asset('storage/list.json'));
}
But if I have a problem (for testing I just add a not correct address) of connection an exception is thrown and I cannot go into "else" part.
So I add a "try, catch":
try{
$response = Http::timeout(2)->get('http.site/file.json');
return $response->body();
}catch (Exception $ex) {
return file_get_contents(asset('storage/pharmaciesList.json'));
}
which is the correct way to treat this kind of code, and is it correct using a try catch without taking care of the exception?
Of course it's the right way, every function that could throw an exception should be enclosed in a try catch block. Otherwise (you said you're using Laravel) you can handle that exception in the exception handler.
Anyone have experience using laravel job with multiple database transaction in one queue?
does laravel support it.
I have an issue, i have 2 different database connection which is database A and database B, when i dispatch my first job using database A everything is working, all my data insert correctly, but when i dispatch my second job using database B , the transaction does not commit and no data insert at all
i need to restart the worker then it will work again.
im using redis as queue driver.
Database A Transaction
$valid = true;
DB::beginTransaction();
try {
//some logic happen here if got error $valid will be false
//if valid true commit else rollback
$valid ? DB::commit() : DB::rollback();
} catch (Exception $e) {
$valid = false;
DB::rollback();
}
Database B Transaction
$valid = true;
DB::beginTransaction('b-connection');
try {
//some logic happen here if got error $valid will be false
//if valid true commit else rollback
$valid ? DB::connection('b-connection')->commit() : DB::connection('b-connection')->rollback();
} catch (Exception $e) {
$valid = false;
DB::connection('b-connection')->rollback();
}
How I dispatch job
DeliveryOrderJob::dispatch($data)->onConnection('swift')->onQueue('do');
Basically both using the same logic, the only different is database connection. Please help.
You don't need to write rollback function in try{}. If that logic will fail or any other error occur then the catch Exception will rollback it.
\DB::connection('b-connection')->beginTransaction();
try {
\DB::connection('b-connection')->commit();
}catch (Exception $e) {
$valid = false;
DB::connection('b-connection')->rollback();
}
I want to update data by batch that always goes to catch. I am using pgsql database.
I followed this tutorial
https://github.com/mavinoo/laravelBatch
$tbc = $this->gradeService->updateGrade($request);
try{
if(count($tbc) > 0)
\Batch::update('grades',$tbc,'id');
}catch(\Exception $e){
return "OOps, an error occured";
}
return back()->with('status', 'Saved');
This part of code always execute catch. How can i solve this problem?
this code shud check login credentials and forward either to logged in page for admin when getParameter(7)=1 or to customer when it is 0..
if login credentials are not correct it will go to error messages and fromt her to login page again.. but somehow it is directly going to errorpage in else case if its not admin!! next two cases are not being checked at all!!
protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
try
{
Class.forName("com.mysql.jdbc.Driver");
Connection con = DriverManager.getConnection("jdbc:mysql://localhost:3306/mutualfund", "root", "");
Statement stmt = con.createStatement();
ResultSet result = stmt.executeQuery("SELECT * FROM login_table;");
String uname= request.getParameter("username");
String pass= request.getParameter("password");
while(result.next())
{
if(result.getString(1).equals(uname) && result.getString(2).equals(pass))
{
if(result.getBoolean(7)==true)
{
response.sendRedirect("displayFunds.jsp");
}
if((result.getBoolean(7)==false) && (result.getString(4).equals("")))
{
response.sendRedirect("changePassword.jsp?name="+uname+"&&pass="+pass);
}
if((result.getBoolean(7)==false) && (!result.getString(4).equals("")))
{
response.sendRedirect("custProfile.jsp");
}
}
else
{
response.sendRedirect("loginFailed.jsp");
}
}
}
catch (Exception ex) {
Logger.getLogger(Admin.class.getName()).log(Level.SEVERE, null, ex);
}
}
}
You're not returning from the method, but continuing to iterate through the while loop. You seem to expect that a simple method call response.sendRedirect() magically aborts the whole while loop and returns from the method. It doesn't do that. The code just continues the loop, checking the next user and setting the redirect URL, hereby overriding the previous one.
You need to return from the method yourself.
response.sendRedirect(someURL);
return;
Your concrete problem is caused because your login doesn't match the last user entry in the DB.
Unrelated to the concrete problem, this approach is however terribly inefficient. You're not taking benefit of the powers of a relational database and instead copying the entire DB table into Java's memory and performing the comparison in Java. You should be writing SQL queries in such way that it returns exactly the information you need. In this particular case, you should be using the SQL WHERE clause instead (in a prepared statement!), so that the resultset contains exactly zero or one row.
if (resultSet.next()) {
// Login OK!
} else {
// Login fail!
}
Further, your code is also leaking DB resources by never closing them. You should be closing them in finally. Also, loading the JDBC driver on every HTTP request is unnecessary. Just load it once during webapp's/servlet's startup.
See also:
Login works only for last user in the database
JDBC always tests the last row of MySQL table?
How often should Connection, Statement and ResultSet be closed in JDBC?