MySQL question
That's what I refering to "not ready for MySQL". My client specifically
asked about MySQL.
Many thanks,
Leslie
> Dear Leslie,
>
> No, I think MM5 is ready but....the documentation to support Third
> Party
> Modules and Third Party Modules themselves are not ready for MySQL.
>
> Thank you,
>
> Nerd Boy
>
> 1-573-292-1136
> <A HREF ="http://www.nerdboyinc.com">http://www.nerdboyinc.com</A>
> <A HREF ="http://www.doyoureallycare.com">http://www.doyoureallycare.com</A>
> <A HREF ="http://www.nbicentral.com">http://www.nbicentral.com</A>
> <A HREF ="http://www.crosstowntraffic.net">http://www.crosstowntraffic.net</A>
> Your alternative source for Miva Merchant Modules
>
> For Customer Service and Support:
> <A HREF ="http://www.nbisupport.com">http://www.nbisupport.com</A>
> or send email to: [email protected]
>
> <A HREF ="http://www.nerdboyproductions.com">http://www.nerdboyproductions.com</A>
> <A HREF ="http://www.asmallurl.com">http://www.asmallurl.com</A>
> <A HREF ="http://www.nbiracing.com">http://www.nbiracing.com</A>
> <A HREF ="http://www.yourlottosite.com">http://www.yourlottosite.com</A>
>
>
>
>> So the bottom line is ... MM5 is not quite ready for MySQL?
>>
>> Leslie
>>
>>
>>> In most scenarios, the MM5 would not need the load balancing across
>>> multiple servers, so the issue would not come up. But when a store
>>> decides it wants that load balancing, there will be database issues
>>> along
>>> with the issue of needing mirror scripts copies of the modules.
>>> Updating
>>> module versions (3rd party and miva core) will be a headache. It is
>>> one
>>> thing for the host to unzip multiple copies of core mvc files, but what
>>> about the new update wizard. It is going to flow the new module
>>> versions
>>> to one location. So you will have one server updated with new scripts
>>> and
>>> others not. It definitely is going to require some sort of technique
>>> to
>>> put all scripts on the single server. If that is done, then it might
>>> not
>>> be an issue with the data either. This is going to be a trial and
>>> error
>>> experimentation. I would hope that hosts share their knowledge rather
>>> than "trade secret" these issues. Film at 11.
>>>
>>>
>>> --
>>> Bill Weiland - Emporium Plus <A HREF ="http://www.emporiumplus.com/store.mvc">http://www.emporiumplus.com/store.mvc</A>
>>> Modules for eCommerce. Mail Mgr, Coupon, Rate This, Wait List Mgr,
>>> PayPal, Gift/Wish List, Froogle data feed, Shipping & dozens more
>>> Online Documentation <A HREF ="http://www.emporiumplus.com/tk3/v3/doc.htm">http://www.emporiumplus.com/tk3/v3/doc.htm</A>
>>> Question <A HREF ="http://www.emporiumplus.com/mivamodule_wcw.mvc?Screen=SPTS">http://www.emporiumplus.com/mivamodule_wcw.mvc?Screen=SPTS</A>
>>> |
>>>
>>> ---- David Hubbard <[email protected]> wrote:
>>>> From: William Weiland
>>>> >
>>>> > The modules within merchant were written that way because
>>>> > they have had a year or two to write them. You know how
>>>> > long we have had since Miva settled on how and where the
>>>> > data would be located and files named. So the suggested
>>>> > first step was to use the old access method for your
>>>
>>>> > module's own configuration and concentrate on the mivasql methods
>>>> for
>>>> > accessing store data (products/cats/orders/etc). The next step,
>>>> which
>>>> > will take considerable time if the module has a lot of configuration
>>>> > databases, will be to convert the module's internal data to mivasql
>>>> > calls.
>>>>
>>>> Ah, I didn't realize that was even an option. That
>>>> definitely would raise some issues with load balancing;
>>>> those considering it would need to ensure that the
>>>> modules they are using have been written using the
>>>> SQL method so no surprises result.
>>>>
>>>> David
>>>>
That's what I refering to "not ready for MySQL". My client specifically
asked about MySQL.
Many thanks,
Leslie
> Dear Leslie,
>
> No, I think MM5 is ready but....the documentation to support Third
> Party
> Modules and Third Party Modules themselves are not ready for MySQL.
>
> Thank you,
>
> Nerd Boy
>
> 1-573-292-1136
> <A HREF ="http://www.nerdboyinc.com">http://www.nerdboyinc.com</A>
> <A HREF ="http://www.doyoureallycare.com">http://www.doyoureallycare.com</A>
> <A HREF ="http://www.nbicentral.com">http://www.nbicentral.com</A>
> <A HREF ="http://www.crosstowntraffic.net">http://www.crosstowntraffic.net</A>
> Your alternative source for Miva Merchant Modules
>
> For Customer Service and Support:
> <A HREF ="http://www.nbisupport.com">http://www.nbisupport.com</A>
> or send email to: [email protected]
>
> <A HREF ="http://www.nerdboyproductions.com">http://www.nerdboyproductions.com</A>
> <A HREF ="http://www.asmallurl.com">http://www.asmallurl.com</A>
> <A HREF ="http://www.nbiracing.com">http://www.nbiracing.com</A>
> <A HREF ="http://www.yourlottosite.com">http://www.yourlottosite.com</A>
>
>
>
>> So the bottom line is ... MM5 is not quite ready for MySQL?
>>
>> Leslie
>>
>>
>>> In most scenarios, the MM5 would not need the load balancing across
>>> multiple servers, so the issue would not come up. But when a store
>>> decides it wants that load balancing, there will be database issues
>>> along
>>> with the issue of needing mirror scripts copies of the modules.
>>> Updating
>>> module versions (3rd party and miva core) will be a headache. It is
>>> one
>>> thing for the host to unzip multiple copies of core mvc files, but what
>>> about the new update wizard. It is going to flow the new module
>>> versions
>>> to one location. So you will have one server updated with new scripts
>>> and
>>> others not. It definitely is going to require some sort of technique
>>> to
>>> put all scripts on the single server. If that is done, then it might
>>> not
>>> be an issue with the data either. This is going to be a trial and
>>> error
>>> experimentation. I would hope that hosts share their knowledge rather
>>> than "trade secret" these issues. Film at 11.
>>>
>>>
>>> --
>>> Bill Weiland - Emporium Plus <A HREF ="http://www.emporiumplus.com/store.mvc">http://www.emporiumplus.com/store.mvc</A>
>>> Modules for eCommerce. Mail Mgr, Coupon, Rate This, Wait List Mgr,
>>> PayPal, Gift/Wish List, Froogle data feed, Shipping & dozens more
>>> Online Documentation <A HREF ="http://www.emporiumplus.com/tk3/v3/doc.htm">http://www.emporiumplus.com/tk3/v3/doc.htm</A>
>>> Question <A HREF ="http://www.emporiumplus.com/mivamodule_wcw.mvc?Screen=SPTS">http://www.emporiumplus.com/mivamodule_wcw.mvc?Screen=SPTS</A>
>>> |
>>>
>>> ---- David Hubbard <[email protected]> wrote:
>>>> From: William Weiland
>>>> >
>>>> > The modules within merchant were written that way because
>>>> > they have had a year or two to write them. You know how
>>>> > long we have had since Miva settled on how and where the
>>>> > data would be located and files named. So the suggested
>>>> > first step was to use the old access method for your
>>>
>>>> > module's own configuration and concentrate on the mivasql methods
>>>> for
>>>> > accessing store data (products/cats/orders/etc). The next step,
>>>> which
>>>> > will take considerable time if the module has a lot of configuration
>>>> > databases, will be to convert the module's internal data to mivasql
>>>> > calls.
>>>>
>>>> Ah, I didn't realize that was even an option. That
>>>> definitely would raise some issues with load balancing;
>>>> those considering it would need to ensure that the
>>>> modules they are using have been written using the
>>>> SQL method so no surprises result.
>>>>
>>>> David
>>>>
Comment