# |
Jul 11th 2018, 13:42 |
verax5 |
page |
# |
Jul 11th 2018, 13:42 |
verax5 |
I don't understand why cakephp is forcing me to create a model when I just want o return static apge.. |
# |
Jul 11th 2018, 13:42 |
iqu |
could open many possibilities with async model |
# |
Jul 11th 2018, 13:42 |
iqu |
anyone tried with cake: https://laravel-news.com/laravel-swoole |
# |
Jul 11th 2018, 13:34 |
dereuromark |
Unsub sounds like straight from criminal minds and behavior unit of the FBI :P doing some cake profiling there? HEHE |
# |
Jul 11th 2018, 13:34 |
josbeir |
and the path is wrong too |
# |
Jul 11th 2018, 13:34 |
josbeir |
your view name is wrong |
# |
Jul 11th 2018, 13:22 |
verax5 |
Which from what I understand should invoke index() method in UnsubController right? |
# |
Jul 11th 2018, 13:22 |
verax5 |
Page I'm trying to load is /unsub |
# |
Jul 11th 2018, 13:22 |
verax5 |
https://kopy.io/0kMSX |
# |
Jul 11th 2018, 13:22 |
verax5 |
Would anyone have any clue why this keeps returning page not found? |
# |
Jul 11th 2018, 12:35 |
josbeir |
just use setDirty('modified', true) if you dont want it to update.. |
# |
Jul 11th 2018, 12:35 |
josbeir |
once your entity is marked as dirty it will be trigged. |
# |
Jul 11th 2018, 12:34 |
josbeir |
it will always be updated, unless you set the field dirty, then it will be ignored. |
# |
Jul 11th 2018, 12:31 |
Diego_ |
but the student have '[dirty]' => ['courses' => true], |
# |
Jul 11th 2018, 12:30 |
Diego_ |
because each of the courses array itens have only this '[dirty]' => ['_joinData' => true], |
# |
Jul 11th 2018, 12:30 |
Diego_ |
hmm i think its the main model trigger |
# |
Jul 11th 2018, 12:25 |
josbeir |
https://book.cakephp.org/3.0/en/orm/behaviors/timestamp.html#saving-updates-without-modifying-timestamps |
# |
Jul 11th 2018, 12:23 |
Diego_ |
how about this exists event in timestamp? |
# |
Jul 11th 2018, 12:23 |
josbeir |
https://book.cakephp.org/3.0/en/orm/saving-data.html#associate-many-to-many-records |
# |
Jul 11th 2018, 12:22 |
Diego_ |
hmm i want timestamp for course only when creating this alone |
# |
Jul 11th 2018, 12:22 |
josbeir |
if you only want to link stuff, you could also use the 'link' method |
# |
Jul 11th 2018, 12:21 |
josbeir |
if you dont want that behavior, you could just disable it before save |
# |
Jul 11th 2018, 12:20 |
josbeir |
if there are dirty fields on the entity the timestamp will be updated. |
# |
Jul 11th 2018, 12:19 |
Diego_ |
Course record already exists im using only its id to create new CoursesMemberships |
# |
Jul 11th 2018, 12:18 |
josbeir |
you are using 'always' and you trigger a save on those entities |
# |
Jul 11th 2018, 12:18 |
tim |
Technically you are making changes though, because its associations will be different |
# |
Jul 11th 2018, 12:16 |
Diego_ |
im not making any change in the main entity only creating new record for the join one |
# |
Jul 11th 2018, 12:16 |
josbeir |
then both models will get timestamp magic |
# |
Jul 11th 2018, 12:16 |
Diego_ |
both models have the behavior |
# |
Jul 11th 2018, 12:15 |
josbeir |
not the associations |
# |
Jul 11th 2018, 12:15 |
josbeir |
it should update the model where the behavior is attached to |
# |
Jul 11th 2018, 12:00 |
Diego_ |
Using the cake book example: Student BelongsToMany Course and Course BelongsToMany Student, when creating a new record for student=>courses(many in the same form) the behavior updates the course modified column too, arent its suposed to update only the join model table? CoursesMemberships |
# |
Jul 11th 2018, 12:00 |
Diego_ |
Hello, im trying to understand the Timestamp behavior using event 'modified' => 'always' with a "through" association. |
# |
Jul 11th 2018, 11:47 |
lorenzo |
yes |
# |
Jul 11th 2018, 10:59 |
magiq |
if event throws exception, code that call dispatch will die or not ? |
# |
Jul 11th 2018, 10:49 |
josbeir |
and i'm lazy |
# |
Jul 11th 2018, 10:49 |
josbeir |
amqp would be my other choice but that would require more work :P |
# |
Jul 11th 2018, 10:49 |
josbeir |
i'll give it a go, seems headache-free enough to me :slightly_smiling_face: |
# |
Jul 11th 2018, 10:46 |
dereuromark |
yes, even fatals are now caught in php7 :slightly_smiling_face: you can run them simultanously, as long as the DB is somewhat transaction safe (inno db should be afaik for mysql) |
# |
Jul 11th 2018, 10:43 |
josbeir |
you just mean that it catches exceptions ? |