ssossossosso

Forums

Covering OroCommerce topics, B2B eCommerce trends, community updates and company announcements.

This topic contains 0 replies, has 1 voice, and was last updated by  o.z.muhsin 2 months, 2 weeks ago.

  • Creator
    Topic
  • #4955

    o.z.muhsin
    Participant

    Assumme one would write an importing functionality just like the way the demo data is being imported.What would be the problem using this approach instead of using the platform approach i.e importexport.yml ?

    E.g Oro\Bundle\ProductBundle\Migrations\Data\Demo\ORM::load

    -> File being read
    -> Class object initialized and data filled in
    -> Flushing the entity

    I am asking this to clear things up as both approach have been used.

Viewing 1 replies (of 1 total)
  • Author
    Replies
  • #6219
    vshutko
    vshutko
    Participant

    Demo data migrations are used to load data needed to demonstrate application features, they are not usable for import/export. But if you want use it for import the main problem is once migration is loaded it is marked as “executed” (see ‘oro_migrations_data’ table) and you can’t execute it once more. So use migrations only if you need to load main data (example of main data – list of countries) or demo data.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.