• Resolved MDesigner0

    (@mdesigner0)


    I’m interested in buying the version that lets you reset order numbers, but I’m concerned about potential database field collisions. Is this an issue?

    Let’s say I have some “dead” order IDs (Woocommerce stores orders as posts, if I’m not mistaken) hanging around the 3000’s. If I use this plugin to reset my order IDs to #1, wouldn’t this collide with abandoned carts in the 3000’s? How does this plugin avoid the order IDs being falsely associated with foreign keys in other tables?

    https://www.ads-software.com/plugins/woocommerce-sequential-order-numbers/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author SkyVerge

    (@skyverge)

    No issues, as this plugin actually is fairly simple and doesn’t support reseting order numbers. It will simply take the highest existing order number and start from there.

    Our premium, paid version, Sequential Order Numbers Pro: https://www.woothemes.com/products/sequential-order-numbers-pro/ offers a lot more control over the format of the order numbers, yet still doesn’t really allow for resetting (without deleting all previous orders).

    Back when we developed these plugins it seemed logical that merchants would never want to reuse order numbers (seems like it would wreak havoc with accounting) but as we’ve gotten occasional requests for this over time, it may be something we look into for the premium plugin in the future.

    Hope that made sense, and thanks for the question!
    Justin

    Thread Starter MDesigner0

    (@mdesigner0)

    Ah, gotcha. So to reset to order #1, it actually deletes all previous orders. That’s fine too. I assume it cleanly deletes all related order info in other tables?

    Plugin Author SkyVerge

    (@skyverge)

    Ah, gotcha. So to reset to order #1, it actually deletes all previous orders.

    Pretty close, though the sequential order numbers plugins themselves do not ever delete an order, that would have to be done manually. You can imagine the outcry if the order numbers plugin were to delete a shop’s orders without the merchant fully understanding/expecting that behavior… bad scene.

    Of course this could be somewhat tedious on a shop with a lot of orders, so this might actually make a decent how-to article with some code, or perhaps a small plugin to purge all orders in one fell swoop. Or maybe even a less drastic measure would be some way of “archiving” them.

    Deleting all orders is definitely in the “with great power, comes great responsibility” category, and would require plenty of disclaimers, but thanks for the idea, we’ll consider it further!

    Justin

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Question about database collisions’ is closed to new replies.