[wp-trac] [WordPress Trac] #22884: What if I delete wp_posts table from database.

[WordPress Trac]

#22884: What if I delete wp_posts table from database.
---------------------------+------------------------------
 Reporter:  mukkundthanki  |       Owner:
     Type:  enhancement    |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Database       |     Version:  3.5
 Severity:  normal         |  Resolution:
 Keywords:  dev-feedback   |     Focuses:
---------------------------+------------------------------
Changes (by jipmoors):

 * keywords:  needs-testing has-patch => dev-feedback


Comment:

 Replying to [comment:10 pento]:
 That was kind of the underlaying thing when I mentioned that I did not
 feel good about putting the require once and dbDelta at that spot. Thanks
 for putting it into words more clearly.

 I did think about the `wp_options`, which would be caught at the
 `is_blog_installed` check, but the `wp_users` slipped by.

 In my research to the problem I did first try to use `repair.php`
 functionality to repair the tables, but since they are missing and not
 broken it obviously didn't work. Which got me wondering if the way this is
 used in `is_blog_installed` is kind of minimal and should be expanded for
 more specific problems and exceptions.

 ''Requesting feedback on:''

 Could somebody argument for me that it's ok to use dbDelta to try and fix
 any and all problems that might be there, or should there be more
 splitting in the definition of SQL/Tables. The only options there are now
 is '''global''' or '''blog/multisite''' inside `wp_get_db_schema()`.

 I just don't know what the possible problems might be when you have a
 ''missing'' table and a ''broken'' table when running dbDelta.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/22884#comment:11>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform