syntaxseed, 16 days ago

Like guys... there isn't a limit on the number of SQL tables you can have. It's not DB golf where fewer tables = better. 🤦‍♀️

syntaxseed, 16 days ago

Exporting a month's worth of media uploads shouldn't be this complicated and shouldn't need a plugin.

The importer should allow me to import just the DB/Meta data if I don't check the 'download & import files' box (importing huge files from a password protected staging site) and allow me to just ftp the actual files up.

Utter nonsense.

So much of #WordPress is actively hostile to the idea of having multiple environments.

alda, 16 days ago

@syntaxseed I agree on all counts. This seems to be for the benefit of the WordPress.com systems rather than anything else. (I.e. not the community.)

Then there's the insistence on WP having write access to itself, how dependencies are managed and how it can't catch up with the newest PHP versions.

thomasfuchs, 16 days ago

@syntaxseed denormalization is the best part of database design, often the more tables the merrier

feld, 16 days ago

@syntaxseed there actually are limits, though? and some operations will take much longer if you have an insane number of tables

MySQL:

> InnoDB permits up to 4 billion tables. (edit: unless your filesystem poops out first)

Postgres:

https://www.postgresql.org/docs/current/limits.html

#pedantic

syntaxseed, 16 days ago

@feld I mean.... if you're approaching 4 billion tables... you got other problems than non-normalized WordPress data. 🤣