Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Populate your table with less rows than default value.
Shrink table to fit your data.
Rebuild.
Save node.
Empty rows are shown in node view.
Go to edit page. Table was actually not rebuilt.
Shrink table again.
Save node.
Rebuild not honored.
Comments
Comment #1
Taxoman CreditAttribution: Taxoman commentedI have postponed trying this module until the module is stable and sufficiently "mature" on D7, and so I have just checked out this issue queue every now and then to get an impression about its state. I am now getting close to deciding to test/evaluate the 2.0 version.
Is this issue still a problem in 2.0 or the latest -dev?
Comment #2
rjacobs CreditAttribution: rjacobs commentedYes, this is still an issue in dev (and 7.x-2.2). This problem also applies when uploading from csv to overwrite existing data when the new data contains fewer rows/columns than the original.
Interestingly when we have entities with more than one tablefield we are able to properly re-size one of those tablefields at a time but not multiple. If we try to update multiple tablefields on the same edit (such that a re-size in involved) only the the last one edited will save properly.
The data inside the "shruken" table is correct after a save, but it's as if the new row/column settings are somehow not persisting to the next rebuild.
Comment #3
rjacobs CreditAttribution: rjacobs commentedIt looks like #2052215: Unlimited cardinality and changing the number of rows/columns (e.g. shrink table size not being honored as old data persists) is actually a more active place to explore this old issue. As a result, I'm going to make this as a dup.