Author Topic: VM DB changes in the 3.2.x series?  (Read 399 times)


  • Jr. Member
  • **
  • Posts: 191
VM DB changes in the 3.2.x series?
« on: August 09, 2018, 09:21:08 am »

Are there any DB schema changes in the VM database in the 3.2.x series?

I am asking because I plan to do a direct VM DB copy of products/orders/etc, from a local site using a slightly older VM 3.2.x version, to a remote site using a fairly recent release.

Any trouble expected?


Studio 42

  • Contributing Developer
  • Sr. Member
  • *
  • Posts: 3751
  • Joomla & Virtuemart developper
    • Studio 42 - Virtuemart & Joomla extentions
  • VirtueMart Version: 2.6 & 3
Re: VM DB changes in the 3.2.x series?
« Reply #1 on: August 09, 2018, 11:07:00 am »
I think that main changes are about params in product_customfields, but field type have changed eg from varchar to text or text to varchar.
In the order items table the param is perhaps saved another way.


  • Virtuemart Projectleader
  • Administrator
  • Super Hero
  • *
  • Posts: 9825
  • VM3.2 Cached and Optimized
    • VM3 Extensions
  • VirtueMart Version: VirtueMart 3 on joomla 3
Re: VM DB changes in the 3.2.x series?
« Reply #2 on: August 20, 2018, 22:56:29 pm »
Just check the svn yourself, it is easy.

I set the maximum of any varchar to 15359, it is the biggest possible number. In future, any varchar which are not keys and are bigger than 1000 or so, will be mediumtext or so.

You can always just execute the table updater. So long it never failed, except when you downgrade with it, then you can get in trouble.
I should fix your bug, please support the VirtueMart project and become a member
Extensions approved by the core team: