| # |
Aug 29th 2019, 15:38 |
 neon1024 |
Yeah perhaps :) |
| # |
Aug 29th 2019, 15:38 |
slackebot2 |
<neon1024> |
| # |
Aug 29th 2019, 15:38 |
neon1024 |
Really? |
| # |
Aug 29th 2019, 15:37 |
graziel |
@neon1024 just add custom script to composer.json |
| # |
Aug 29th 2019, 15:34 |
ricksaccous |
but maybe too much magic is bad sometimes |
| # |
Aug 29th 2019, 15:33 |
ricksaccous |
bin/cake schema_cache clear |
| # |
Aug 29th 2019, 15:33 |
ricksaccous |
i've just made it habit to do |
| # |
Aug 29th 2019, 15:33 |
ricksaccous |
yeah that would be cool |
| # |
Aug 29th 2019, 15:27 |
neon1024 |
Feels like it would be handy addition |
| # |
Aug 29th 2019, 15:26 |
neon1024 |
Should migrations clear orm cache after it’s run? |
| # |
Aug 29th 2019, 13:58 |
neon1024 |
José’s plugin ;P |
| # |
Aug 29th 2019, 13:57 |
alexdd55976 |
perfect |
| # |
Aug 29th 2019, 13:57 |
alexdd55976 |
oh.. :) |
| # |
Aug 29th 2019, 13:56 |
neon1024 |
Which is what the plugin does |
| # |
Aug 29th 2019, 13:54 |
alexdd55976 |
@neon1024 you could do a afterSave in AppModel and save the originalData and newData in a versioning table, adding user_id and timestamp. versioning done |
| # |
Aug 29th 2019, 13:47 |
admad |
i bet a single A4 won't cut it :slightly_smiling_face: |
| # |
Aug 29th 2019, 13:45 |
neon1024 |
Time for pencil and paper! |
| # |
Aug 29th 2019, 13:45 |
neon1024 |
...but I’d have to update foreignkeys or duplicate associations |
| # |
Aug 29th 2019, 13:45 |
neon1024 |
I’m just thinking about hooking beforeSave to duplicate the record, then allow the save. Then swapping the duplicate to live and setting the saved to pending |
| # |
Aug 29th 2019, 13:44 |
admad |
the one submitting later wouldn't have seen the edit done earlier if it's still pending approval |
| # |
Aug 29th 2019, 13:43 |
admad |
things get even wackier when multiple people submit an edit |
| # |
Aug 29th 2019, 13:40 |
neon1024 |
Very true! |
| # |
Aug 29th 2019, 13:40 |
admad |
on the bright side at least you dont have to implement this where records are translated :P |
| # |
Aug 29th 2019, 13:40 |
steinkel |
lol, about the confusion, I remember working on a similar case in cake2 using https://github.com/lorenzo/cakephp-logstash |
| # |
Aug 29th 2019, 13:40 |
admad |
don't remember for sure, check it |
| # |
Aug 29th 2019, 13:39 |
neon1024 |
Oh really? Okay, thanks :slightly_smiling_face: |
| # |
Aug 29th 2019, 13:39 |
admad |
right, i think associations are always marked dirty |
| # |
Aug 29th 2019, 13:39 |
neon1024 |
Like adding a new Tag to a Post |
| # |
Aug 29th 2019, 13:39 |
neon1024 |
That’s a lot of `if()` statements |
| # |
Aug 29th 2019, 13:39 |
neon1024 |
Yeah, but across say 3 associations as well? |
| # |
Aug 29th 2019, 13:38 |
admad |
well if a record is dirty some field has changed |
| # |
Aug 29th 2019, 13:38 |
neon1024 |
..but I’d have to detect changes in the entity and it’s associations |
| # |
Aug 29th 2019, 13:37 |
neon1024 |
Perhaps duplicatable would be better as I could set the status |
| # |
Aug 29th 2019, 13:36 |
neon1024 |
The specification says that any change generates a new version, which is pending and then gets signed off |
| # |
Aug 29th 2019, 13:36 |
admad |
i can confirm duplicatable can handle associations :slightly_smiling_face: |
| # |
Aug 29th 2019, 13:36 |
neon1024 |
Just increment the version and duplicate the whole thing |
| # |
Aug 29th 2019, 13:36 |
neon1024 |
I thought it would be easier with Duplicatable |
| # |
Aug 29th 2019, 13:35 |
admad |
they are both José, but the author of that version plugin is savant not lorenzo |
| # |
Aug 29th 2019, 13:35 |
neon1024 |
Did I? Oh geez, so I did. Apologies José I meant Jose |
| # |
Aug 29th 2019, 13:34 |
admad |
you got the wrong Jose :slightly_smiling_face: |
| # |
Aug 29th 2019, 13:34 |
neon1024 |
Any advantages to storing the versions in other tables? Why wouldn’t you just version in the same table? |