Paul Craig
2013-08-29 06:01:39 UTC
Hi all,
I started a Symfony project earlier this summer and I've encountered my
fair share of problems while learning it (nearly always human error), but I
can't find the solution for my most recent one anywhere and would
appreciate some help.
I've been using command line Doctrine commands in Symfony 2.3.3 to create
and update the tables in an offsite phpMyAdmin database for a number of
weeks now.
I'm running my Symfony app on a local Apache server (included in the XAMPP
bundle) on a Windows 8 machine.
For the most part, I've found Symfony really well put-together and am
starting to greatly appreciate Doctrine.
However, since just a few hours ago (at least, that's when I first noticed
it) doctrine's update command (ie "php app/console doctrine:schema:update
--force") now takes an excruciating amount of time to run. Whereas it has
habitually took 4-5 seconds to complete, updating my schema with doctrine
now clocks in at about 7 minutes.
I recently defragmented my hard drive as well as updated to the latest
version of git (I'm using git bash for a console), and it was only after
this that I noticed doctrine having slowed down. (To be fair, I haven't
updated my database tables in a few days.)
I've updated Symfony to 2.3.4 as well as checked out some code from about a
week ago to see if it would change anything, but it hasn't (not that I was
expecting it to, but I figured I might as well try).
Curiously, "php app/console doctrine:schema:drop --force" also takes quite
a long time (~3m15s), whereas "php app/console doctrine:schema:create" is
still quite zippy at ~3s.
I don't really know what to do, because obviously updating/dropping the
tables still works, it just takes bloody ages.
I'm sure it'll come down to some fundamental detail I'm missing, but I
would rather feel dumb and fix this than have it stay like this.
I'm happy to post more specifics if I've neglected to include something
important.
Turrah,
Paul
--
--
If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security
You received this message because you are subscribed to the Google
Groups "Symfony2" group.
To post to this group, send email to symfony2-/***@public.gmane.org
To unsubscribe from this group, send email to
symfony2+unsubscribe-/***@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/symfony2?hl=en
---
You received this message because you are subscribed to the Google Groups "Symfony2" group.
To unsubscribe from this group and stop receiving emails from it, send an email to symfony2+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
I started a Symfony project earlier this summer and I've encountered my
fair share of problems while learning it (nearly always human error), but I
can't find the solution for my most recent one anywhere and would
appreciate some help.
I've been using command line Doctrine commands in Symfony 2.3.3 to create
and update the tables in an offsite phpMyAdmin database for a number of
weeks now.
I'm running my Symfony app on a local Apache server (included in the XAMPP
bundle) on a Windows 8 machine.
For the most part, I've found Symfony really well put-together and am
starting to greatly appreciate Doctrine.
However, since just a few hours ago (at least, that's when I first noticed
it) doctrine's update command (ie "php app/console doctrine:schema:update
--force") now takes an excruciating amount of time to run. Whereas it has
habitually took 4-5 seconds to complete, updating my schema with doctrine
now clocks in at about 7 minutes.
I recently defragmented my hard drive as well as updated to the latest
version of git (I'm using git bash for a console), and it was only after
this that I noticed doctrine having slowed down. (To be fair, I haven't
updated my database tables in a few days.)
I've updated Symfony to 2.3.4 as well as checked out some code from about a
week ago to see if it would change anything, but it hasn't (not that I was
expecting it to, but I figured I might as well try).
Curiously, "php app/console doctrine:schema:drop --force" also takes quite
a long time (~3m15s), whereas "php app/console doctrine:schema:create" is
still quite zippy at ~3s.
I don't really know what to do, because obviously updating/dropping the
tables still works, it just takes bloody ages.
I'm sure it'll come down to some fundamental detail I'm missing, but I
would rather feel dumb and fix this than have it stay like this.
I'm happy to post more specifics if I've neglected to include something
important.
Turrah,
Paul
--
--
If you want to report a vulnerability issue on Symfony, please read the procedure on http://symfony.com/security
You received this message because you are subscribed to the Google
Groups "Symfony2" group.
To post to this group, send email to symfony2-/***@public.gmane.org
To unsubscribe from this group, send email to
symfony2+unsubscribe-/***@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/symfony2?hl=en
---
You received this message because you are subscribed to the Google Groups "Symfony2" group.
To unsubscribe from this group and stop receiving emails from it, send an email to symfony2+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.