Home  >  Article  >  Backend Development  >  10 recommended articles about PDO::ERRMODE_SILENT

10 recommended articles about PDO::ERRMODE_SILENT

黄舟
黄舟Original
2017-06-11 10:03:361119browse

Use exception mode -PDO::ERRMODE_EXCEPTION (Method 3 for capturing errors in SQL statements in PDO) exception mode will create a PDOException and set the erorCode attribute, which can encapsulate the execution code into a try{...}catch In the {...} statement, uncaught exceptions will cause the script to interrupt and display a stack trace to let the user understand where the problem occurred! In the first two articles "Using the default mode-PDO::ERRMODE_SILENT (Method 1 to capture errors in SQL statements in PDO)" and "Using warning mode-PDO::ERRMODE_WARNING (Method 2 to capture errors in SQL statements in PDO)" We have introduced two methods: default mode and exception mode, so today we will introduce the third method to capture errors in SQL statements in PDO ~ Another very useful thing about exception mode is that it can be clearer than traditional PHP style warnings You can easily build your own error handling, and exception mode requires less code/nesting than silent mode and explicitly checking the return value of each database call. Except

1. Recommended articles about exception patterns

10 recommended articles about PDO::ERRMODE_SILENT

# #Introduction: Use exception mode -PDO::ERRMODE_EXCEPTION (Method 3 to capture errors in SQL statements in PDO) Exception mode will create a PDOException and set the erorCode attribute, which can encapsulate the execution code into a try{...}catch In the {...} statement, uncaught exceptions will cause the script to interrupt and display a stack trace to let the user understand where the problem occurred! In the first two articles "Using the default mode-PDO::ERRMODE_SILENT(Capturing S in PDO...

2. Recommended articles about PDO::ERRMODE_EXCEPTION

10 recommended articles about PDO::ERRMODE_SILENT

Introduction: Using exception mode-PDO::ERRMODE_EXCEPTION (Capturing errors in SQL statements in PDO three) exceptions The mode will create a PDOException and set the erorCode attribute, which can encapsulate the execution code into a try{...}catch{...} statement. The uncaught exception will cause the script to interrupt and display the stack trace to let the user Understand where the problem occurs! In the first two articles "Using the default mode-PDO::ERRMODE_SILENT(PDO to capture S...

3. How to errorCode() Use? Summary of errorCode() instance usage

10 recommended articles about PDO::ERRMODE_SILENT

Introduction: Method 1 of error handling in PDO-errorCode( ) method in PDO has two methods for obtaining error information in the program: errorCode() method and errorInfo() method! In the next article, we will introduce these two methods to you one by one! Here are three ways to capture errors in SQL statements in PDO. If you are still unfamiliar or don’t understand, you can review "Using the default mode - PDO::ERRMODE_SILENT (Methods to capture errors in SQL statements in PDO 1.. .

##4.

Use the default mode-PDO::ERRMODE_SILENT (Method 1 to capture errors in SQL statements in PDO)

10 recommended articles about PDO::ERRMODE_SILENT Introduction: There are three options to choose from to capture SQL statement errors in PDO. Choose the appropriate solution to capture SQL statement errors according to your own development project and actual situation. Error!

##5. Capturing SQL statements in PDO

Introduction: Capturing SQL statements in PDO Error in: Use the default mode -----PDO::ERRMODE_SILENT to set the errorCode attribute of the PDOStatement object in the default mode, but do not perform any other operations. For example: add data to the database through the prepare() and execute() methods. , set the erroCode attribute of the PDOStatement object, and manually detect errors in the code. The steps are as follows $dbms=mysql;//Database type. $dbName=admin;//Database used

The above is the detailed content of 10 recommended articles about PDO::ERRMODE_SILENT. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn