Performance impact of creating tables in SQLite

Question

In SQLite, there is a CREATE TABLE IF NOT EXISTS clause.

I can't find a reason why this is not good to use performance-wise.

For every SQLite query, I call this beforehand to make things easier.

Since SQLite is very fast, is there any problem with doing this? Is this just bad practice VS is there actually a performance bottleneck?

If that helps, I'm using this with PHP 7

Answer 1

Use a database migration tool, such as https://phinx.org/, which can run your DML at deployment time. Database modifications should not be done by the user at runtime, even if the DML execution time is negligible