I have two content sets defined, as an example:
SetOne has 165 rows, SetTwo has 82 rows. From the UI the import and clearing of these rows goes perfectly. I run the import, the content appears on my site, I clear the set and the content disappears.
BUT, in the database the behavior is that when I import the number of rows in my Node table increases by the appropriate amount (165 or 82, depending on the set I run), but when I clear it the Node table row count is decreasing only by a small portion of the number it should (only removing 52 and 15 respectively). This occurs every time I do an import then clear and though the nodes are not appearing on the site I am troubled by the database bloat that this is causing.
Any ideas?
Comments
Comment #1
robbieferrero commentedAlso, when running migrate on a set that has a destination of Terms or Users, from the database perspective, it is working perfectly. I only seem to be seeing this behavior with the migration of nodes.
Comment #2
robbieferrero commentedThis isn't a fix, but my solution to this problem was to set, in my table wizard views, Duplicate to Yes - to filter duplicate entries. This suppressed this behavior entirely, though the NID autoincrement just continues to rise without being reset (not sure that that behavior is even an issue/feature/bug or not, doesn't have an effect on the current project.
Comment #3
mikeryanYour source view does need to have a single row per node to be created - if you have joins that create duplicates, you need to use DISTINCT.
Auto-increment values are not reset when rows are deleted - this is standard database behavior, so ids are not reused.