You’re not alone. It still amazes me how many members here cling to using DEPRECATED mysql_ because seeing OOP and mysqli_ together in the same context bothers them.
mysqli_ procedural is the logical step to take if OOP isn’t an option.
At times I feel like posting an ALL CAPS reply
“For goodness sake, write mysql_ out of your code soon especially if you’re rewriting the code anyway!”
The only one at the moment that sticks out to me is using prepared statements. I recently (a few months back helping someone with prepared statements), found out that you cannot use procedural prepared statements with OOP connection. What amazes me the most is there’s such a thing for procedural in the first place. I thought prepared statements was strictly for OOP style hence prepared statements, but I was wrong. http://php.net/manual/en/mysqli.prepare.php
I’m not sure exactly why you can’t do this if you can mix match procedural and OOP together, but I’m assuming because using prepared statements are specific to which connection they are opened with.
That makes sense since the SQL you prepare has to be processed ready to be executed )possibly multiple times) at a later time.
When I switched from mysql_ to mysqli_ calls I set up the connection OOP style and just converted the select calls to use procedural style queries to start with. The insert, update and delete calls all got updated to OOP prepare statements. Next step is to convert the select statements to use OOp prepare statements (if I don’t decide to swap to PDO first).