| # |
Jun 13th 2019, 15:30 |
 ricksaccous |
yeah there's only one migration then right? |
| # |
Jun 13th 2019, 15:30 |
noel |
yes but not by name... just `bin/cake migrations migrate` |
| # |
Jun 13th 2019, 15:30 |
ricksaccous |
i would do this on a test db btw XD |
| # |
Jun 13th 2019, 15:29 |
ricksaccous |
and then ran it? |
| # |
Jun 13th 2019, 15:29 |
ricksaccous |
then you deleted every table in your db |
| # |
Jun 13th 2019, 15:29 |
ricksaccous |
okay |
| # |
Jun 13th 2019, 15:29 |
noel |
yes, it was created and it looks correct |
| # |
Jun 13th 2019, 15:29 |
ricksaccous |
to assure your migration was created? |
| # |
Jun 13th 2019, 15:29 |
ricksaccous |
did you end up checking your config/Migrations folder |
| # |
Jun 13th 2019, 15:27 |
noel |
oops.. repeat message |
| # |
Jun 13th 2019, 15:27 |
noel |
Not really understanding migrations. I created a migration from my db using `bin/cake bake migration_snapshot`, then I cleared my db to test the migration and ran `bin/cake migrations migrate` |
| # |
Jun 13th 2019, 15:25 |
admad |
When you need to work with large number of records like for e.g. bulk updates use the db layer directly instead of ORM |
| # |
Jun 13th 2019, 15:24 |
admad |
@val it's not a "problem". Just how PHP works. Objects take more memory than arrays. You shouldn't be pulling/creating 153000 entities at a time. |
| # |
Jun 13th 2019, 15:24 |
chris-andre |
@val Just a input: you can use `->enableHyadration(false)` to return array results. |
| # |
Jun 13th 2019, 15:21 |
neon1024 |
Do you have debug mode on? That will increase memory usage quite a bit |
| # |
Jun 13th 2019, 15:20 |
neon1024 |
Also, an entity is an object |
| # |
Jun 13th 2019, 15:18 |
neon1024 |
Collections didn’t exist in Cake 2 though |
| # |
Jun 13th 2019, 15:13 |
val |
Hi, I just discovered that Cake 3.x Entity objects use 2 times more memory than Cake 2.x associative arrays and 4 times more memory than plain PHP objects. Tested with 153000 items collection. Is it a known problem? Are there any plans to improve memory usage? https://gist.github.com/nikic/5015323 |
| # |
Jun 13th 2019, 14:41 |
swimboy |
And thanks, using 4.x-dev worked perfectly. |
| # |
Jun 13th 2019, 14:40 |
swimboy |
I have an app that I’ve built in 3.7, and have a short-term need for a small subset of it as a separate app. I figured it would be a good test-case for the alpha release. |
| # |
Jun 13th 2019, 14:39 |
neon1024 |
I should upgrade my test app to alpha2 also! Good reminder |
| # |
Jun 13th 2019, 14:39 |
neon1024 |
But as you say we’ve no idea what @swimboy is trying out! Good job testing the alphas though :thumbsup: |
| # |
Jun 13th 2019, 14:38 |
neon1024 |
I prefer it for testing the release as it’s a fixed point for the core team to work from, whereas a commit hash can be a little more frustrating I think |
| # |
Jun 13th 2019, 14:38 |
dereuromark |
if its just about testing things this would be fine |
| # |
Jun 13th 2019, 14:38 |
neon1024 |
https://semver.mwl.be/#?package=cakephp%2Fcakephpandversion=4.0.0-alpha2andminimum-stability=alpha |
| # |
Jun 13th 2019, 14:38 |
dereuromark |
you could also just use 4.x-dev :slightly_smiling_face: I do that |
| # |
Jun 13th 2019, 14:36 |
neon1024 |
Don’t you need to specify special releases exactly? |
| # |
Jun 13th 2019, 14:33 |
swimboy |
Is there a reason that I can install 4.0.0-alpha1 via composer, but not alpha2? I used the command `composer create-project --prefer-dist cakephp/app:4.0.0-alpha1 myproject`. And even `composer update` won’t pick up alpha2 from an installation of alpha1. |
| # |
Jun 13th 2019, 14:29 |
ricksaccous |
what lars said |
| # |
Jun 13th 2019, 14:29 |
ricksaccous |
yeah |
| # |
Jun 13th 2019, 14:28 |
ricksaccous |
you need the NameOfMigration |
| # |
Jun 13th 2019, 14:28 |
lars.ebert |
If it is empty or contains no commands, then something went wrong when creating the migration. |
| # |
Jun 13th 2019, 14:28 |
ricksaccous |
to the bin/cake bake migration_snapshot NAmeOfMigration |
| # |
Jun 13th 2019, 14:28 |
lars.ebert |
@noel Take a look into the config/migrations folder. There you should see a file for your migration snapshot. If you open that file, you should see the migration that `bake` created for you. |
| # |
Jun 13th 2019, 14:28 |
ricksaccous |
are you sure the migration was even created in the first place because you are supposed to add an argument |
| # |
Jun 13th 2019, 14:26 |
ricksaccous |
seems your snapshot wasn't that good then i suppose |
| # |
Jun 13th 2019, 14:26 |
ricksaccous |
when he tried to run the migration again |
| # |
Jun 13th 2019, 14:26 |
ricksaccous |
if he deleted the whole db it should have worked |
| # |
Jun 13th 2019, 14:22 |
dereuromark |
use "migrations status" to check for details on each step |
| # |
Jun 13th 2019, 14:21 |
dereuromark |
or did you also clear those? |
| # |
Jun 13th 2019, 14:21 |
dereuromark |
they have been marked as migrated for a reason there |