Problem installing Doctrine DBAL provider about cmf-sandbox HOT 15 CLOSED

use php composer.phar install dev not update ..

from cmf-sandbox.

I have the same problem:

My sequence of commands are:

git clone git://github.com/symfony-cmf/cmf-sandbox.git
cd cmf-sandbox
cp app/config/parameters.yml.dist app/config/parameters.yml
cp app/config/phpcr_doctrine_dbal.yml.dist app/config/phpcr.yml
curl -s http://getcomposer.org/installer | php --
php composer.phar require jackalope/jackalope-doctrine-dbal:dev-master

from cmf-sandbox.

did you revert the composer.lock that was updated?

from cmf-sandbox.

ah i see we are actually suggesting to use update in the README .. i will fix that. but when i do that i don't get the issue you are noting. however i am seeing couple issues when loading the fixtures:

• "General error: 1364 Field 'sort_order' doesn't have a default value"
• "Item / not found in workspace default"

@dbu and @petesiss

from cmf-sandbox.

btw the issue you are noted above is now tracked here schmittjoh/JMSDiExtraBundle#28

hopefully we can figure out what is going wrong with the fixture loading tomorrow.

from cmf-sandbox.

Strange. Ive just done a fresh install of the sandbox with doctrine dbal, but I'm not getting either of those errors. Fixtures appear to be loading ok for me and sandbox appears to be functional.

Also tested the fixtures on our own project and they seem fine.

The jackalope repo in the composer.lock is one commit behind where it should be for the sandbox, but that commit doesn't seem to make any difference for me on whether the fixtures load.

from cmf-sandbox.

I am getting the feeling that this approach of using "require" to add the dependency is too flaky because it ends up doing an "update" afterwards since the new dependency isn't in the "composer.lock" file.

from cmf-sandbox.

Id not come across "require" until now. If its only purpose is to avoid users downloading libs they may not use, even if it wasn't flakey Id say for the sandbox better to simplify the install instructions for the dbal version by just including it by default.

Could always put a note at the end to suggest users can remove the implementation they're not using if they're worried about having the redundant code.

from cmf-sandbox.

yeah .. i will switch to using "require-dev"

from cmf-sandbox.

argh .. now i see again why i used the "require" command .. since the midgard dependency requires a php extension. so i am switching things for doctrine dbal only for now. we could of course provide multiple composer.lock files.

maybe @Seldaek has an idea for now to best do this ..

from cmf-sandbox.

@lsmith77 I'm not sure what this is about, but the require command is a bit buggy. It takes the current versions from what's installed instead of the lock file, so when it updates the newly required package, it can rollback stuff (compared to the lock) which isn't too good.

from cmf-sandbox.

Also that means if you have nothing installed, it's basically ignoring the lock file I think.

from cmf-sandbox.

@jordillonch i fixed some issues in the Doctrine DBAL to address the fixture loading issues I saw. i have also updated the docs to use php composer.phar install --dev instead of the require.

so please revert any local changes you might have, ensure that the tables are deleted again from your database (optionally use app/console doctrine:phpcr:init:dbal --drop) and then try again.

hope all will work then.

from cmf-sandbox.

please reopen if the issue isn't fixed yet

from cmf-sandbox.

Thank you Lukas! Now it's working :)

from cmf-sandbox.