Barand

@KHS I agree that SELECT * should not be used, but those "rows" you mentioned are "columns".

Don't use deprecated html markup, such as font color. Use style attribute. echo "<p style='font-size:4pt; color:#ffffff'>$echo</p>"; or define a class for those links in your css .mylink { font-size: 4pt; color: #FFFFFF; } then echo "<p class='mylink'>$echo</p> NOTE: I have no way of knowing what $echo contains. If it contains <a> tag then the styling will need to be applied there and not to the <p>

Take $values out of the subject

Your script needs a "base time" - the time from which you are counting. Instead of always starting your timer from 00:00:00 you would first calculate the time elapsed from the base time and start from there. EG base time = 09:00, and it is now 11:10:35, so your timer should start from "02:10:35" when it loads. If you next open the page at midday then the timer shoud start from "03:00:00"

so why would you expect to find it by defining a path starting with "inc/"?

Input fields also work better when they have "name" attributes

1. As you are putting multiple names in the message it doesn't make sense to include (one of) them in the subject. 2. Your while loop should be while ($values = mysqli_fetch_array($result)) { otherwise you trash the $msg variable by overwriting it.

Autocommit! Yes, that's the whole idea behind transactions and committing or rolling back . try public function multiInsert($data) { $errorList = []; $stmt = $this->conn->prepare("INSERT INTO user (username, email, passwd) VALUES (?,?,?)"); foreach ($data as $rec) { try { $stmt->execute($rec); } catch (PDOException $ex) { $errorList[] = [ $rec, $ex->errorInfo[1], $ex->getMessage() ]; } } return $errorList; }

Don't set autocommit to false. BeginTransaction will cancel it for the duration of the transaction until a commit or rollback is called. Don't commit every insert, do one commit after all the inserts are executed (or rollback if there was an exception) Don't save plaintext passwords. Use password_hash() and password_verify() I have rewritten your code (working, for me at any rate) <?php class wrapper { private $conn; public function __construct($con) { $this->conn = $con; } public function multiInsert($data) { $this->conn->beginTransaction(); try { $stmt = $this->conn->prepare("INSERT INTO user (username, email, passwd) VALUES (?,?,?)"); foreach ($data as $rec) { $stmt->execute($rec); } $this->conn->commit(); } catch (PDOException $e) { $this->conn->rollback(); throw $e; } } } const HOST = 'localhost'; const USERNAME = '...'; const PASSWORD = '...'; const DBNAME = '...'; // PDO database connection // $dsn = "mysql:dbname=".DBNAME."; host=".HOST."; charset=utf8"; $db = new pdo($dsn, USERNAME, PASSWORD, [ PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION, PDO::ATTR_EMULATE_PREPARES => false, PDO::ATTR_DEFAULT_FETCH_MODE => PDO::FETCH_ASSOC ]); $data = array ( array ( "jdoe1", "[email protected]", "abc1"), array ( "jdoe2", "[email protected]", "abc2"), array ( "jdoe3", "[email protected]", "abc3"), array ( "jdoe4", "[email protected]", "abc4"), array ( "jdoe5", "[email protected]", "abc5"), ); $wrap = new wrapper($db); $wrap->multiInsert($data); /* RESULTS mysql> select * from user; +--------+----------+----------------+--------+ | userid | username | email | passwd | +--------+----------+----------------+--------+ | 1 | jdoe1 | [email protected] | abc1 | | 2 | jdoe2 | [email protected] | abc2 | | 3 | jdoe3 | [email protected] | abc3 | | 4 | jdoe4 | [email protected] | abc4 | | 5 | jdoe5 | [email protected] | abc5 | +--------+----------+----------------+--------+ */ ?>

As an aside, is there a good administrative front-end for PostgreSQL (MySQL Workbench equivalent - modelling, admin, editing etc)?

If you are going to have a column for sequencing, take a tip from someone who used to program on paper then have their lines of code transferred to punch cards - sequence in increments of, say, 100 and not 1. That leaves lots of room to alter the sequence or add inserts.

Also, change the order of the code in your page, putting the php section first. Code flow should be something like this if POST data exists Validate data storing error messages if no errors do updates header("location: #") // reload page exit end if end if if GET data process GET data endif any other code necessary for building page e.g. menus !DOCTYPE html html output any validation error messages form form fields end form end html

Nearly - you need to test $del[$key], not just $del

E.G. $res = $conn->query("SELECT i.model_id , i.model_name , c.category_id as cat_id , c.model_category_name as cat_name FROM model_index i JOIN models_category_ids USING (model_id) JOIN models_category c USING (category_id) "); $data = []; foreach ($res as $r) { if (!isset($data[$r['model_id']])) { $data[$r['model_id']] = [ 'name' => $r['model_name'], 'cats' => [] ]; } $data[$r['model_id']]['cats'][$r['cat_id']] = $r['cat_name']; } /* $data = Array ( [1] => Array ( [name] => John Doe [cats] => Array ( [1] => IT Devloper [3] => Mechanic ) ) [2] => Array ( [name] => Laura Norder [cats] => Array ( [2] => Photographer ) ) ) */

The link in your code is to the model_id Add "i.model_id" to the selected columns in the query, then the output will have $model->model_id If you need individual category_ids, revert your query to that getting several rows for each model and store the results in an array, indexed by model, so each model has an array of categories.

My query returns two output columns model_name cats Try echo model->model_name . " " . $model->cats . "<br>"; (of course, without seeing the code that actually runs the query and gets the results, that's just a guess.)

Which is line 19?

One way is with GROUP_CONCAT() SELECT i.model_name , GROUP_CONCAT(c.category_id,' ',c.model_category_name SEPARATOR ', ') as cats FROM model_index i JOIN models_category_ids USING (model_id) JOIN models_category_tbl c USING (category_id) GROUP BY i.model_id;

... or as you are using mysqli, put this line before your connection creation mysqli_report(MYSQLI_REPORT_ERROR|MYSQLI_REPORT_STRICT);

Below is an extract from the mysql reference manual As you can see, with the exceptions of "PRIMARY KEY" and "FOREIGN KEY" (which can be considered to be reserved phrases) the terms "index" and "key" are interchangeable.

That would the meet the requirement for "logical, meaningful and unique". Beware name clashes though. They (constraint names) need to be unique within the scope of the database schema. Table alias name scope is only the query.

As with the example I gave earlier for an index name (idx_xxx_yyy) then use similar for, say, foreign key constraints (FK_xxx_yyy) Keep them logical, meaningful and unique (eg FK_Pinocchio )

Disney character names for constraints

To me it sounds like I don't name them because they will be given reasonable names automatically

I'm surprised it got past the prepare statement before giving an error. Where do $id and $row come from? Are the two sections of code above related in any way? If, say, you want to add 3 records inserting post_id and category_id into each then the query that gets prepared should look like "INSERT INTO posts_category_ids (post_id, category_id) VALUES (?,?),(?,?),(?,?)"