Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Liam Sorsby
    @liamsorsby
    Are there any known bugs when dumping then loading the same dump file into the database concerning foreign keys?
    I appologise if this is the wrong place to ask
    Marc J. Schmidt
    @marcj
    Try it. ;o)
    Liam Sorsby
    @liamsorsby
    I have, and I get a constraint error on the foreign key
    Marc J. Schmidt
    @marcj
    Well, then you answered yourself the first question.
    Liam Sorsby
    @liamsorsby
    The question was are there any known bugs, not is it a bug.
    Do you want me to submit it as a bug with the schema and fixture?
    Marc J. Schmidt
    @marcj
    No, we don’t have a list of Known bugs for "dumping then loading the same dump file into the database"
    If it’s a bug in Propel, then sure!
    Serg N. Kalachev
    @ksn135
    Hi there, everyone!
    Please tell me, do we have an option in propel.ini to permanently exclude from migration process all tables from a specific connection (one of the several) ?
    Serg N. Kalachev
    @ksn135
    TIL that's very easy to kill production database from devops computer with simple one-liner: modify schema.yml and then execute "propel:diff && propel:up"...
    Maxime Corson
    @Maxooo
    @ksn135 This is a very good question. You can use the "connection" option of the propel:migration:(generate-)diff command to generate the right SQL diff. You can eventually create a bash script (diff.sh) that will execute this command to avoid mistakes.
    Gregor Harlan
    @gharlan
    What is best practice for symfony form validation (sf2 + propel2)? Do you use a valdation.yml file?
    Maxime Corson
    @Maxooo
    @gharlan I prefer explicit validation declaration in FormType class, but this is not the community common way to use validation... Ex :
    $builder->add('subject', null, array(
                    'label' => "Subject",
                    'required' => true,
                    'constraints' => array(
                        new NotBlank(),
                    )   
                ));
    Maxime Corson
    @Maxooo
    But I found one exception : you can't use the UniqueObject constraint with this method and need to use the validation.yml file.
    AppBundle\Model\ProjectUser:
        constraints:
            - Propel\PropelBundle\Validator\Constraints\UniqueObject:
                fields: [project_id, user_id]
                message: "A similar record already exists."
    Serg N. Kalachev
    @ksn135
    For several years I worked with Propel and Symfony 1.x. Last two years I worked with Symfony 2.x and doctrine. What about current state of integration between Symfony 3.x и Propel ? I wanna return to my roots! ))
    ravitulala
    @ravitulala
    i just started reading propel documentation
    i didnt get where t o run that xml code
    could anyone please guide me how to start with it...and how the flow