Eos database converter

[David M. Graham]

Excellent.

I'm looking forward to putting this to active use.

David

[zip1]

Since the original post, I have gotten the products and orders  portions code and initial testing done.

Tom

[zip1]

The difference is that EOS use ISO country and state codes instead of just ID numbers to identify countries and states.   The old codes are converted to the ISO codes during the conversion.

As an example the old United states code was 223, the new code is US. Using the old way if for some reason the id number 223 was changed you would end up with a miss match in other parts of the cart . This problem did not occur often but it could be expensive to fix.  The other advantage is that when bridges are created to other application it creates a common ground for  the data to be moved and used between the applications.

[David M. Graham]

Tom,

I'm presuming that the address book speed is a bit lower than the customer record speed because of the need to adjust for multiple default addresses per customer in EOS.  Just how is this being managed??

David
 

[zip1]

As with any flexible project things do change. Previously we stated that we didn't plan on producing a store converter until the 0.6 version of EOS was released.

 For several weeks I have been actively working on a Database converter.

  There will be two main frameworks, a single store converter for the store owner that just wants to convert there store and a Enterprise version that will contain all the single store libraries with extra features that is intended for hosting sites.

some initial results of a conversion of a 6.2 b2b store:
address_book ~ 16.45330095 secs ~  14,675  records
customers ~ 9.115972995 secs ~  12,153 records
customers_info ~ 5.166297912 ~ 12,153 records

customers_groups ~ 0.002246856 secs ~  1 record
customers_groups_disc ~ 0.002246856 secs ~ 1 record

The framework of the converters are being designed so that they will work with any mysql database. If your store should happen to use a different database engine, as long as the data can be put into a mysql database then it can have a library written for it to be converted to EOS

Tom O'Neill