Log message #4158049

# At Username Text
# Jul 11th, 13:22 verax5 Would anyone have any clue why this keeps returning page not found?
# Jul 11th, 12:35 josbeir just use setDirty('modified', true) if you dont want it to update..
# Jul 11th, 12:35 josbeir once your entity is marked as dirty it will be trigged.
# Jul 11th, 12:34 josbeir it will always be updated, unless you set the field dirty, then it will be ignored.
# Jul 11th, 12:31 Diego_ but the student have '[dirty]' => ['courses' => true],
# Jul 11th, 12:30 Diego_ because each of the courses array itens have only this '[dirty]' => ['_joinData' => true],
# Jul 11th, 12:30 Diego_ hmm i think its the main model trigger
# Jul 11th, 12:25 josbeir https://book.cakephp.org/3.0/en/orm/behaviors/timestamp.html#saving-updates-without-modifying-timestamps
# Jul 11th, 12:23 Diego_ how about this exists event in timestamp?
# Jul 11th, 12:23 josbeir https://book.cakephp.org/3.0/en/orm/saving-data.html#associate-many-to-many-records
# Jul 11th, 12:22 Diego_ hmm i want timestamp for course only when creating this alone
# Jul 11th, 12:22 josbeir if you only want to link stuff, you could also use the 'link' method
# Jul 11th, 12:21 josbeir if you dont want that behavior, you could just disable it before save
# Jul 11th, 12:20 josbeir if there are dirty fields on the entity the timestamp will be updated.
# Jul 11th, 12:19 Diego_ Course record already exists im using only its id to create new CoursesMemberships
# Jul 11th, 12:18 josbeir you are using 'always' and you trigger a save on those entities
# Jul 11th, 12:18 tim Technically you are making changes though, because its associations will be different
# Jul 11th, 12:16 Diego_ im not making any change in the main entity only creating new record for the join one
# Jul 11th, 12:16 josbeir then both models will get timestamp magic
# Jul 11th, 12:16 Diego_ both models have the behavior
# Jul 11th, 12:15 josbeir not the associations
# Jul 11th, 12:15 josbeir it should update the model where the behavior is attached to
# Jul 11th, 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, 12:00 Diego_ Hello, im trying to understand the Timestamp behavior using event 'modified' => 'always' with a "through" association.
# Jul 11th, 11:47 lorenzo yes
# Jul 11th, 10:59 magiq if event throws exception, code that call dispatch will die or not ?
# Jul 11th, 10:49 josbeir and i'm lazy
# Jul 11th, 10:49 josbeir amqp would be my other choice but that would require more work :P
# Jul 11th, 10:49 josbeir i'll give it a go, seems headache-free enough to me :slightly_smiling_face:
# Jul 11th, 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, 10:43 josbeir you just mean that it catches exceptions ?
# Jul 11th, 10:43 josbeir and what do you mean 'not in php7' ?
# Jul 11th, 10:43 josbeir @dereuromark and its no problem that these workers run simultaneously
# Jul 11th, 10:36 dereuromark but I tend to use 5-10 min frames to start new workers, and let them run for about twice as long.
# Jul 11th, 10:35 dereuromark no, not in php7
# Jul 11th, 10:35 cjquinn I’ve used your plugin in production @dereuromark. Its very good, so tyvm!
# Jul 11th, 10:34 josbeir @dereuromark i'm guessing that if a job in the worker crashes, the whole worker crashes with it ?
# Jul 11th, 10:32 josbeir i do like the aproach of that plugin and it is actively maintained
# Jul 11th, 10:32 neon1024 At least you know where to find @dereuromark to get support! :,)
# Jul 11th, 10:31 josbeir hmm :slightly_smiling_face:
# Jul 11th, 10:31 dereuromark And it works better on real servers rather than heroku I discovered :P