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

jgraham’s picture

Status: Active » Closed (won't fix)

derieppe,

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.

derieppe’s picture

Hi,

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 ?)

checker’s picture

Version: 5.x-1.2 » 6.x-2.0-beta2
Status: Closed (won't fix) » Active

Hi,

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.

checker’s picture

Component: User interface » Code
traviscarden’s picture

Agreed. 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.

XiaN Vizjereij’s picture

Subscribe and +1 for this one.

colan’s picture

Subscribing, and +1 from me too.

colan’s picture

I 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.

skizzo’s picture

Subscribing

traviscarden’s picture

The 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.

deekayen’s picture

It's not an unreasonable expectation to have such a config option, but I'm waiting for a patch to talk about.

deekayen’s picture

Version: 6.x-2.0-beta2 » 7.x-1.x-dev

Bumping version.

  • Nafes committed 1c821e4 on feature-tables
    Issue #305963 by Nafes: Made admin form changes and added new variable.
    

  • Nafes committed eb27b95 on feature-tables
    Issue #305963 by Nafes: Made table processing in consistency with 'All...

  • Nafes committed 1c821e4 on 7.x-1.x
    Issue #305963 by Nafes: Made admin form changes and added new variable.
    
  • Nafes committed eb27b95 on 7.x-1.x
    Issue #305963 by Nafes: Made table processing in consistency with 'All...
Nafes’s picture

Assigned: Unassigned » Nafes
Issue summary: View changes
Status: Active » Fixed

The issue has been fixed in 7.x-1.x-dev release. The fix has been made in consistency with #5.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.