I want to generate insert to table from query but this query might throw a division by zero error:

insert into rpp
select IFNULL(IF((IF(((((((`s`.`smi` + `s`.`jmb`) + `s`.`ruah`) +
`s`.`stg_jd`) + `s`.`jdw_pro`) / `p`.`rate`) <= 2),
((`p`.`rate` * 4) - ((((`s`.`smi` + `s`.`jmb`) + `s`.`ruah`) 
+ `s`.`stg_jd`) + `s`.`jdw_pro`)),0) > 0),
(FLOOR((IF(((((((`s`.`smi` + `s`.`jmb`) + `s`.`ruah`) 
+ `s`.`stg_jd`) + `s`.`jdw_pro`) / `p`.`rate`) <= 2),
((`p`.`rate` * 4) - ((((`s`.`smi` + `s`.`jmb`) + 
`s`.`ruah`) + `s`.`stg_jd`) + `s`.`jdw_pro`)),
0) / `p`.`bets`)) * `p`.`bets`),0),0) AS `rp`
FROM (`produk` `p`LEFT JOIN `stok` `s` ON ((`p`.`kode` = `s`.`kode_produk`)))
Thanks in advance!
There are multiple ways to solve this.
Add logic, that you divide by 1 instead or however you want to handle it. For this there's this wonderful function IF() which works like IF(condition, then, else), for example IF(my_column = 0, 1, my_column).
Another way is by setting your sql_mode accordingly. Have a look at the sql_mode error_for_division_by_zero.
  
The ERROR_FOR_DIVISION_BY_ZERO mode affects handling of division by
  zero, which includes MOD(N,0). For data-change operations (INSERT,
  UPDATE), its effect also depends on whether strict SQL mode is
  enabled.
  
If this mode is not enabled, division by zero inserts NULL and produces no warning.
  
If this mode is enabled, division by zero inserts NULL and produces a warning.
  
If this mode and strict mode are enabled, division by zero produces an error, unless IGNORE is given as well. For INSERT IGNORE
  and UPDATE IGNORE, division by zero inserts NULL and produces a
  warning. 
  
For SELECT, division by zero returns NULL. Enabling
  ERROR_FOR_DIVISION_BY_ZERO causes a warning to be produced as well,
  regardless of whether strict mode is enabled.
  
As of MySQL 5.7.4, ERROR_FOR_DIVISION_BY_ZERO is deprecated. In MySQL
  5.7.4 through 5.7.7, ERROR_FOR_DIVISION_BY_ZERO does nothing when named explicitly. Instead, its effect is included in the effects of
  strict SQL mode. In MySQL 5.7.8 and later, ERROR_FOR_DIVISION_BY_ZERO
  does have an effect when named explicitly and is not part of strict
  mode, as before MySQL 5.7.4. However, it should be used in conjunction
  with strict mode and is enabled by default. A warning occurs if
  ERROR_FOR_DIVISION_BY_ZERO is enabled without also enabling strict
  mode or vice versa. For additional discussion, see SQL Mode Changes in
  MySQL 5.7.
  
Because ERROR_FOR_DIVISION_BY_ZERO is deprecated, it will be removed
  in a future MySQL release as a separate mode name and its effect
  included in the effects of strict SQL mode.
Related Solutions
Php – How to prevent SQL injection in PHP

The correct way to avoid SQL injection attacks, no matter which database you use, is to separate the data from SQL, so that data stays data and will never be interpreted as commands by the SQL parser. It is possible to create SQL statement with correctly formatted data parts, but if you don't fully understand the details, you should always use prepared statements and parameterized queries. These are SQL statements that are sent to and parsed by the database server separately from any parameters. This way it is impossible for an attacker to inject malicious SQL.
You basically have two options to achieve this:
Using PDO (for any supported database driver):
 
 $stmt = $pdo->prepare('SELECT * FROM employees WHERE name = :name');
 $stmt->execute([ 'name' => $name ]);
 foreach ($stmt as $row) {
     // Do something with $row
Using MySQLi (for MySQL):
 
 $stmt = $dbConnection->prepare('SELECT * FROM employees WHERE name = ?');
 $stmt->bind_param('s', $name); // 's' specifies the variable type => 'string'
 $stmt->execute();
 $result = $stmt->get_result();
 while ($row = $result->fetch_assoc()) {
     // Do something with $row
If you're connecting to a database other than MySQL, there is a driver-specific second option that you can refer to (for example, pg_prepare() and pg_execute() for PostgreSQL). PDO is the universal option.
Correctly setting up the connection
Note that when using PDO to access a MySQL database real prepared statements are not used by default. To fix this you have to disable the emulation of prepared statements. An example of creating a connection using PDO is:
$dbConnection = new PDO('mysql:dbname=dbtest;host=127.0.0.1;charset=utf8', 'user', 'password');
$dbConnection->setAttribute(PDO::ATTR_EMULATE_PREPARES, false);
$dbConnection->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
In the above example the error mode isn't strictly necessary, but it is advised to add it. This way the script will not stop with a Fatal Error when something goes wrong. And it gives the developer the chance to catch any error(s) which are thrown as PDOExceptions.
What is mandatory, however, is the first setAttribute() line, which tells PDO to disable emulated prepared statements and use real prepared statements. This makes sure the statement and the values aren't parsed by PHP before sending it to the MySQL server (giving a possible attacker no chance to inject malicious SQL).
Although you can set the charset in the options of the constructor, it's important to note that 'older' versions of PHP (before 5.3.6) silently ignored the charset parameter in the DSN.
Explanation
The SQL statement you pass to prepare is parsed and compiled by the database server. By specifying parameters (either a ? or a named parameter like :name in the example above) you tell the database engine where you want to filter on. Then when you call execute, the prepared statement is combined with the parameter values you specify.
The important thing here is that the parameter values are combined with the compiled statement, not an SQL string. SQL injection works by tricking the script into including malicious strings when it creates SQL to send to the database. So by sending the actual SQL separately from the parameters, you limit the risk of ending up with something you didn't intend.
Any parameters you send when using a prepared statement will just be treated as strings (although the database engine may do some optimization so parameters may end up as numbers too, of course). In the example above, if the $name variable contains 'Sarah'; DELETE FROM employees the result would simply be a search for the string "'Sarah'; DELETE FROM employees", and you will not end up with an empty table.
Another benefit of using prepared statements is that if you execute the same statement many times in the same session it will only be parsed and compiled once, giving you some speed gains.
Oh, and since you asked about how to do it for an insert, here's an example (using PDO):
$preparedStatement = $db->prepare('INSERT INTO table (column) VALUES (:column)');
$preparedStatement->execute([ 'column' => $unsafeValue ]);
Can prepared statements be used for dynamic queries?
While you can still use prepared statements for the query parameters, the structure of the dynamic query itself cannot be parametrized and certain query features cannot be parametrized.
For these specific scenarios, the best thing to do is use a whitelist filter that restricts the possible values.
// Value whitelist
// $dir can only be 'DESC', otherwise it will be 'ASC'
if (empty($dir) || $dir !== 'DESC') {
   $dir = 'ASC';
    
Mysql –  concatenate multiple MySQL rows into one field

You can use GROUP_CONCAT:
SELECT person_id,
   GROUP_CONCAT(hobbies SEPARATOR ', ')
FROM peoples_hobbies
GROUP BY person_id;
As Ludwig stated in his comment, you can add the DISTINCT operator to avoid duplicates:
SELECT person_id,
   GROUP_CONCAT(DISTINCT hobbies SEPARATOR ', ')
FROM peoples_hobbies
GROUP BY person_id;
As Jan stated in their comment, you can also sort the values before imploding it using ORDER BY:
SELECT person_id, 
       GROUP_CONCAT(hobbies ORDER BY hobbies ASC SEPARATOR ', ')
FROM peoples_hobbies
GROUP BY person_id;
As Dag stated in his comment, there is a 1024 byte limit on the result. To solve this, run this query before your query:
SET group_concat_max_len = 2048;
Of course, you can change 2048 according to your needs. To calculate and assign the value:
SET group_concat_max_len = CAST(
                     (SELECT SUM(LENGTH(hobbies)) + COUNT(*) * LENGTH(', ')
                           FROM peoples_hobbies
                           GROUP BY person_id) AS UNSIGNED);
            
Related Question
Mysql – How to output MySQL query results in CSV format
Python – How to connect to a MySQL Database in Python
Mysql – Should I use the datetime or timestamp data type in MySQL
Mysql – How to get a list of user accounts using the command line in MySQL
Mysql – How to reset AUTO_INCREMENT in MySQL
Mysql – How to get the sizes of the tables of a MySQL database
MySQL error code: 1175 during UPDATE in MySQL Workbench
Mysql – How to import an SQL file using the command line in MySQL