search and replace dry run NOT the same as database

  • I did a dry run using better search and replace to go from http to https
    I got 238 cells or instances of
    https://domain.com being replaced with https://domain.com .

    To compare:
    When I tried using migrate DB plugin by the same company with a search and replace
    of the above domain and exported the db to an sql file and did a find for
    https://domain.com in the file showed 706 cells! I know one of them is a comment, but something doesn’t look correct.

    ???? I have used migrate db (plugins by the same company) many times and know lots of people who use it and this is a very large discrepancy between this and better search and replace plugin.

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Peppermintcrisp

    (@webdancer123)

    So, I tried the plugin search and replace by Inpsyde GmbH and for a dry run I
    got 230 cells. options 22, postmeta 19, posts 189. ??

    Thread Starter Peppermintcrisp

    (@webdancer123)

    For the plugin better search and replace by for a dry run I
    got 238 cells. options 31, postmeta 19, posts 188. ??

    Thread Starter Peppermintcrisp

    (@webdancer123)

    ok. I get it for some of this. What is going on is that these are the rows not the cells. A cell in a row can contain many instances. However, I’m still getting weird results for the options table. in better search and replace after running it 2 times I got two different values: 1st 28 and then 31 rows!? Then is search and replace plugin I got 31 and then in the interconnect script I get 21. So, that is a little concerning.
    The postmeta and posts tables have the same number of rows.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘search and replace dry run NOT the same as database’ is closed to new replies.