Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Marcin Pietrzak

    (@iworks)

    why always data migration at every update

    @alerion2

    I’m sorry but this is the very first time when I migrate data in this plugin.

    Marcin

    Thread Starter alerion2

    (@alerion2)

    terrible plugin, i just discovered it created 5000 IDs for nothing…. our order number in woocommerce went from 24000 to 30000 due to your plugin

    Plugin Author Marcin Pietrzak

    (@iworks)

    terrible plugin, i just discovered it created 5000 IDs for nothing…. our order number in woocommerce went from 24000 to 30000 due to your plugin

    @alerion2

    It’s only reflecting price changes. Before version 3 the same data was in postmeta instead post table. And selecting from postmeta consume more resources.

    M

    Thread Starter alerion2

    (@alerion2)

    i don’t think it is a best practice to use post table, and you should have alerted users in some ways. If all the plugins would do like you did, we will end up with IDs in the millions.

    Plugin Author Marcin Pietrzak

    (@iworks)

    i don’t think it is a best practice to use post table

    Why?

    and you should have alerted users in some ways.

    How can I achieve this?

    If all the plugins would do like you did, we will end up with IDs in the millions.

    Does it change anything?

    Thread Starter alerion2

    (@alerion2)

    never heard about notifications? and yes it changes a lot, IDs are used for order numbers etc. and more important things that not storing a single number

    Plugin Author Marcin Pietrzak

    (@iworks)

    I’m sorry for disappointing you.

    You can always fork the last 2.x.x version and develop it. This plugin is open source and GPL.

    Marcin

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘why always data migration at every update’ is closed to new replies.