Database (MySQL) unexpected error appears on the page?

How to prevent unexpected errors from the database (MySQL) in the framework?
For example, I have two excel table upload functions here. Of course, the excel receiving data processing methods written by me in the two places are different, but as you know, the names of some fields in the database cannot be empty. If the two places Excel files are uploaded interchangeably, then a SQL error will appear at this time, as shown below:

1. Wouldn’t it be too troublesome if I had to make a corresponding judgment in the database that every data received in a field cannot be empty?

2. My excel table upload function only corresponds to one method, which is one-to-one. Because my excel structure is different, one method corresponds to one type of excel structure processing.

So I want to find a solution that can block the sql error from appearing on the page. Please give me some advice.

Reply content:

How to prevent unexpected errors from the database (MySQL) in the framework?
For example, I have two excel table upload functions here. Of course, the excel receiving data processing methods written by me in the two places are different, but as you know, the names of some fields in the database cannot be empty. If the two places Excel files are uploaded interchangeably, then a SQL error will appear at this time, as shown below:

1. Wouldn’t it be too troublesome if I had to make a corresponding judgment in the database that every data received in a field cannot be empty?

2. My excel table upload function only corresponds to one method, which is one-to-one. Because my excel structure is different, one method corresponds to one type of excel structure processing.

So I want to find a solution that can block the sql error from appearing on the page. Please give me some advice.

It’s not that database errors cannot be blocked, but it’s not necessary, and it will create more problems. Since it makes sense that a certain field cannot be Null, if you insist on writing it in, what should you do when you get to this place when processing later? It can also be seen from this that you did not check the validity of the data before performing the insertion. The uploaded data is equivalent to the data entered by the user, and dirty data must be prevented from entering.
The usual processing logic is:
Read the csv line by line, use verification rules to verify the data, if ok, store it in $success, otherwise, store it in $bad. Depending on the business logic, when $bad is not empty, the list may be displayed first to ask the user Confirm that illegal data is discarded, and some directly traverse and insert the data in $success, and then generate a report on which ones have been inserted and which ones have not been processed.

Since you have CSV in multiple formats, you should naturally check whether the currently uploaded CSV is consistent with the processing method. Otherwise, what if it is actually saved? I really don’t recommend being lazy.

Just use try {}catch (Exception $e){} to catch exceptions

If you have a framework, you should be able to turn off the debug mode. Logically speaking, it can be automatically blocked.
If you want to manually set the empty field to the default value in the code, you can write a filter yourself, and determine whether it is empty in the filter. If so, give a default value.

1. You can define a default value such as 0 during database design. 2. When inserting this data in the program, you ensure that the user_id field has a value.

If this field is allowed to be null in production, then change the table

If it is not allowed, the error message indicates that there is a problem with the data, and ignore is dangerous. You should

ensure that the source data is not null instead of rudely ignoring