Php5.6.15 I wrote an SQL statement for batch database insertion, which is very long. filtering SQL statements with preg_replace will cause the program to crash and there is no error record. the system log reports an error in php5ts. dll. I am fine if SQL is a little short. Even if the backtracing limit is exceeded, what should not be... php5.6.15
I wrote an SQL statement for batch database insertion, which is very long. filtering SQL statements with preg_replace will cause the program to crash, and there is no error record. in this case, the php5ts. dll error is reported in the system log. I am fine if SQL is a little short.
Should I return a failure even if it exceeds the backtracking limit? How can it crash?
Has anyone ever met? What's going on?
Reply content:
Php5.6.15
I wrote an SQL statement for batch database insertion, which is very long. filtering SQL statements with preg_replace will cause the program to crash, and there is no error record. in this case, the php5ts. dll error is reported in the system log. I am fine if SQL is a little short.
Should I return a failure even if it exceeds the backtracking limit? How can it crash?
Has anyone ever met? What's going on?
I have tested how to write more than 7000 simple data records in batches at a time. This will take a long time, just insert data multiple times.
I don't know if you want to insert an edge or replace an insert. you should separate them! Then, record the logs to see where the problem occurred.