0 votes

I have been trialing your software for the last 2 weeks, however my trial has come to an end.
I hope to soon have the money available to purchase your software on a permanent basis but for the time being the bank balance doesn't allow. Having spent the past 2 weeks working on a model I was slightly dismayed to find the .yml exports I had done only contained the mappings between each entity. Like the following:

Products:
  type: entity
  fields:
    id:
      id: true
      type: integer
      generator:
        strategy: AUTO
  oneToMany:
    productsRecipes:
      targetEntity: Products2Recipes
      mappedBy: products
    suppliersProducts:
      targetEntity: Suppliers2Products
      mappedBy: products
    productsDishes:
      targetEntity: Products2Dishes
      mappedBy: products

My design had 20 seperate columns in that entity..

I was hoping there would be a way of importing .skipper files to Mysql Workbench but all I can find is ways of doing it the other way round.

asked Mar 4, 2015 in General Questions by Doug (200 points)
edited Oct 13, 2015 by ludek.vodicka

1 Answer

0 votes
Best answer

Hi,

we're not considering such export because from our users' point of view it's useless. As soon as you will start using Skipper there is no reason to export it back to workbench.

In case you want to purchase Skipper but don't have whole amount right now, we can offer you purchasing the Skipper license in six continuous payments. Feel free to write us to support@skipper18.com and one of my colleague will send you more details.

Ludek

answered Mar 4, 2015 by ludek.vodicka Skipper developer (120,030 points)
selected Mar 5, 2015 by Doug

Like I've said before, as soon as I can spare £38 a month I will be doing just that (purchasing the 6 month incremental version). For the time being this is not an option money couldn't be tighter as a chef supporting a family of 4, 38 is almost a weeks worth of meals which we struggle with alone.

Have you any remarks on why when Skipper was in Doctrine2 + Symfony2 mode, it would export .yml files not in the format required by Doctrine, and also lacking any columns. The expected result was more along the lines of:

AppBundle\Entity\Product:
    type: entity
    table: Product
    repositoryClass: AppBundle\Entity\ProductRepository
    id:
        id:
            type: integer
            generator: { strategy: AUTO }
    fields:
      size:
        type: decimal
        precision: 50
        scale: 10
        nullable: true
      cost:
        type: decimal
        presision: 10
        scale: 4
        nullable: true
      discount:
        type: decimal
        presision: 2
        scale: 2
        nullable: true
      costunit:
        type: decimal
        presision: 30
        scale: 10
        nullable: true
      created_at:
        type: datetime
      updated_at:
        type: datetime
        nullable: true
    manyToOne:
        user:
          targetEntity: Application\Sonata\UserBundle\Entity\User
          joinColumn:
            name: u_id
            referencedColumnName: id
        foodcat:
          targetEntity: Foodcats
          joinColumn:
            name: p_id
            referencedColumnName: id
        measure:
          targetEntity: Measures
          joinColumn:
            name: m_id
            referencedColumnName: id
        prodlist:
          targetEntity: Prodlist
          joinColumn:
            name: prodlist_id
            referencedColumnName: id
            inversedBy: prodlist

This is really strange because format you described is exactly what Skipper should export. Can you send me your project file where this problem occurred so I can check it? Please send it to ludek.vodicka@skipper18.com