Re: MIVA Merchant 5 Bugs?
Miva is ignoring their own table structure.
I was writing some code when I realized that Miva isn't using it's own table structure. If I create an attribute with options in Miva Admin (like a drop down menu or a radio button), s01_Options.product_id is never supplied and the DB Connector defaults it to 0. The option is still associated with the correct attribute via s01_Options.attr_id which is the associated with a product via s01_Attributes.product_id, but if Miva made the choice to unnormalize the data and associate the option with the product directly, why did they stop? It's not a big deal at all, just an extra join clause in my SQL, but it was misleading and I at least wanted to make everyone else aware.
Miva is ignoring their own table structure.
I was writing some code when I realized that Miva isn't using it's own table structure. If I create an attribute with options in Miva Admin (like a drop down menu or a radio button), s01_Options.product_id is never supplied and the DB Connector defaults it to 0. The option is still associated with the correct attribute via s01_Options.attr_id which is the associated with a product via s01_Attributes.product_id, but if Miva made the choice to unnormalize the data and associate the option with the product directly, why did they stop? It's not a big deal at all, just an extra join clause in my SQL, but it was misleading and I at least wanted to make everyone else aware.
Comment