Hi,
BD maintenance is a nice module but we need to go in his steetings and select new tables when adding a new module.
Could it be possible to have an option "Select all tables automatically" so we don't have to go and select tables one by one ?
Thanks.
Comments
Comment #1
jgraham commentedderieppe,
In general most browsers let you click the first item in a multi-select, then, while holding the shift key down click another item in the list and all items in between will also be selected.
Comment #2
derieppe commentedHi,
Yes you can select all tables by his way. But you need to go to the DB Maintenance settings by the IHM.
What i ask for is an "automatic" selection off table without humain action... (during cron ?)
Comment #3
checker commentedHi,
I also miss this feature. It would be nice if there is a checkbox 'all tables' on settings page. If activated the cron function uses all tables in the database instead of selected tables. So your module need no maintenance itself.
Comment #4
checker commentedComment #5
traviscarden commentedAgreed. Just to clarify, the requested feature here is not a UI enhancement for merely selecting all the options in the SELECT box. It's the option to not rely on user selection because, as it is, every time a module adds a table to the database, you have to come back here and select it to be optimized on cron run. What we're asking for is the option to automatically optimize all tables in the database without having to select them first.
Comment #6
XiaN Vizjereij commentedSubscribe and +1 for this one.
Comment #7
colanSubscribing, and +1 from me too.
Comment #8
colanI just saw this in the README file: "This should probably NOT be used to optimize every table in your Drupal installation." ...with no explanation why. I'm going to try it and see what happens.
Also, I'll see if I can throw a patch together for this.
Comment #9
skizzo commentedSubscribing
Comment #10
traviscarden commentedThe maintainer seems to imply that the reason it's not a good idea to enable on every table is because of the resources that doing so could consume on cron runs. There's some question now whether InnoDB tables should be optimized at all: #1013434: Create alternate optimization for InnoDB. Alternatively, there's some interesting discussion of a dynamic table selection method at #568790: Add automatic option for optimizing tables.
Comment #11
deekayen commentedIt's not an unreasonable expectation to have such a config option, but I'm waiting for a patch to talk about.
Comment #12
deekayen commentedBumping version.
Comment #16
Nafes commentedThe issue has been fixed in 7.x-1.x-dev release. The fix has been made in consistency with #5.