Log message #4192271

# At Username Text
# Jul 8th 2019, 12:40 half2me @dereuromark nope, no exceptions. When I turn of atomicity, everything works as expected
# Jul 8th 2019, 12:15 neothermic it's a cake 1.2 app that got upgraded to 2.x
# Jul 8th 2019, 12:15 neothermic :)
# Jul 8th 2019, 12:15 admad "we got about 1.5k lines in our appmodel" @neothermic you sure someone isn't actively trying to sabotage the project?
# Jul 8th 2019, 11:33 neothermic ah, we cheated, we make a singleton of the userclass for the currently logged in user :)
# Jul 8th 2019, 11:26 neon1024 Thanks to all the contributors of muffin/footprint your ideas just helped me solve a similar problem <3
# Jul 8th 2019, 10:30 dereuromark where there any exceptions or errors encountered? or does it also happen in happy case?
# Jul 8th 2019, 10:26 half2me I remember talking with someone here about it before, I think it was you :)
# Jul 8th 2019, 10:26 half2me @dereuromark do you remember having a similar issue?
# Jul 8th 2019, 10:25 half2me if I have some more time on my hands, I’ll try to trace it with the debugger and see if I can come up with anything useful
# Jul 8th 2019, 10:24 half2me the thing is, I have about 5 findOrReplace functions running in there, and 4 of the succeed, its only the last one which doesnt
# Jul 8th 2019, 10:24 half2me but I’ve come across this in two independent projects now
# Jul 8th 2019, 10:23 half2me and just saying, “oh it doesnt work in my code” is not really something usefull
# Jul 8th 2019, 10:23 half2me I would, but I haven’t been able to reproduce it with a minimal code base
# Jul 8th 2019, 10:23 neon1024 ..and ensure there isn’t a test-case for this
# Jul 8th 2019, 10:23 neon1024 Perhaps you should open an issue with some example code
# Jul 8th 2019, 10:23 half2me it saves correctly when it is disabled
# Jul 8th 2019, 10:22 half2me exactly
# Jul 8th 2019, 10:22 neon1024 However, with atomic false working it probably isn’t a validation issue
# Jul 8th 2019, 10:22 half2me as atomicity would be required for something running in my afterSave transaction
# Jul 8th 2019, 10:22 neon1024 Usually things like that, in my experience, are that something has failed validation and the transaction is rolled back. Usually a validation failure in an associated table
# Jul 8th 2019, 10:22 half2me for now I’ve just left the `['atomic' => false]` option in there, but this is not a proper solution
# Jul 8th 2019, 10:21 half2me yet I remember this exact scenario a few months ago when trying to debug something else
# Jul 8th 2019, 10:21 half2me @neon1024 I searched, but found nothing
# Jul 8th 2019, 10:11 neon1024 @half2me Github issues would be the place to look; in the cakephp/cakephp project
# Jul 8th 2019, 10:11 neon1024 @neothermic AppTable I presume
# Jul 8th 2019, 10:02 half2me wondering if this issue is tracked somewhere
# Jul 8th 2019, 10:02 half2me @dereuromark I think you suggested passing in this option to me a couple of months ago when I was having this problem for the first time
# Jul 8th 2019, 10:02 half2me if I pass in the `['atomic' => false]` option, it works fine
# Jul 8th 2019, 10:02 half2me somtimes it will return an entity which is not persisted
# Jul 8th 2019, 10:01 half2me When calling `findOrCreate()` inside a transaction
# Jul 8th 2019, 10:01 half2me hey guys, I found a weird bug, which I know has come up before, but I’m not sure if it has been fixed in later versions of CakePHP. I’m currently on 3.7.15 on a project.
# Jul 8th 2019, 09:55 neothermic we got about 1.5k lines in our appmodel. no idea where they'll go when we move to 3.x :)
# Jul 8th 2019, 09:49 neon1024 Awww, AppModel :,)
# Jul 8th 2019, 09:42 neothermic we put ours in the appmodel, so it is always enforced
# Jul 8th 2019, 09:42 challgren I did behavior loaded with the Auth tenant_id in the config, so it was all automatic
# Jul 8th 2019, 09:41 neon1024 That might well be a component or trait or behaviour
# Jul 8th 2019, 09:41 challgren @neon1024 beforeFind that added tenant_id
# Jul 8th 2019, 09:40 neon1024 Oh, I haven’t even got onto the queries yet
# Jul 8th 2019, 09:40 neothermic @neon1024 we implemented this with a beforeFind that looked into the query and at the table(s) in use in the query, and added a condition to it for the establishment_id if the query didn't already have one
# Jul 8th 2019, 09:34 neon1024 I still feel like with Authorize class is the best spot