| # |
Apr 19th 2019, 18:05 |
 swimboy |
frozendate |
| # |
Apr 19th 2019, 18:03 |
ricksaccous |
@swimboy after you patchEntity is the date field a frozentime or frozendate object? |
| # |
Apr 19th 2019, 18:02 |
swimboy |
@ricksaccous I am calling patchEntity but it was still trying to stuff "4/19/2019" into the date field in my MariaDB table and spitting out SQL errors. |
| # |
Apr 19th 2019, 18:01 |
admad |
No it doesn't, home page is just the default value |
| # |
Apr 19th 2019, 17:48 |
waspinator |
how would you redirect to the requesting page after logging in using the Authentication plugin? The [example](https://github.com/cakephp/authentication/blob/master/docs/en/migration-from-the-authcomponent.rst#login-action) always redirects to the pages home display |
| # |
Apr 19th 2019, 17:47 |
ricksaccous |
as far as displaying dates that's completely up to you to use the Cake Libs available to you |
| # |
Apr 19th 2019, 17:46 |
ricksaccous |
done |
| # |
Apr 19th 2019, 17:46 |
ricksaccous |
third step - save |
| # |
Apr 19th 2019, 17:46 |
ricksaccous |
second step - patch entity, your request data becomes a frozenDate object |
| # |
Apr 19th 2019, 17:46 |
ricksaccous |
so first step - request data |
| # |
Apr 19th 2019, 17:45 |
ricksaccous |
you can safely save a FrozenTime object and cake will translate it however it needs to |
| # |
Apr 19th 2019, 17:45 |
ricksaccous |
@swimboy generally when you save dates and you patchEntity cake will transform the date into a FrozenTime object |
| # |
Apr 19th 2019, 17:37 |
swimboy |
Couldn't quite figure it out, though. |
| # |
Apr 19th 2019, 17:37 |
swimboy |
OK. I just saw the `Time::niceFormat` section in the book, and thought maybe that would help make things more straightforward. |
| # |
Apr 19th 2019, 17:36 |
NickBusey |
Sounds about right to me |
| # |
Apr 19th 2019, 17:35 |
slackebot |
right way to do it. Any suggestions? |
| # |
Apr 19th 2019, 17:35 |
swimboy |
I'm a little lost regarding displaying dates and storing them in my database. I want to display them (and have the user enter them) as "04/19/2017" but the database wants them stored as "2017-04-19." I've originally set `Cake\I18n\Date::setToStringFormat('yyyy-MM-dd');` in my bootstrap, and then use a function to convert any date field in POST requests to the SQL format before saving the record. It works, but it sure doesn't feel like the |
| # |
Apr 19th 2019, 11:55 |
admad |
the autocomplete is contextual and it will list only methods of current class, so it's not like you are going to get multiple "create" in the list |
| # |
Apr 19th 2019, 11:53 |
mehov |
I thought having a noun first would kind of help when you're looking up that function in the list (so it'd all get sorted by it), but I guess that's not important |
| # |
Apr 19th 2019, 11:52 |
admad |
no need for "createAccount() |
| # |
Apr 19th 2019, 11:51 |
admad |
I would actually drop the noun too. Cause for eg. $this->Accounts->create() is good enough |
| # |
Apr 19th 2019, 11:51 |
mehov |
Got it, thanks a lot! |
| # |
Apr 19th 2019, 11:51 |
admad |
nmv, using the verb first is common practice |
| # |
Apr 19th 2019, 11:50 |
admad |
in which class? |
| # |
Apr 19th 2019, 11:49 |
mehov |
Hi guys, what do you think would be a better practice, naming methods `createAccount()` and `deleteAccount()` or `accountCreate()` and `accountDelete()`? Checked book.cakephp.org/3.0/en/intro/conventions.html and it says *While you can route multiple word controllers in any way you like*. Nothing on https://www.dereuromark.de/2010/10/08/complete-cakephp-naming-conventions/ either |
| # |
Apr 19th 2019, 11:15 |
asdfgh |
thanks |
| # |
Apr 19th 2019, 11:15 |
asdfgh |
ok |
| # |
Apr 19th 2019, 11:07 |
royalty |
and then you can add caching to those, using findBy is just a quick convenience method that you should probably avoid |
| # |
Apr 19th 2019, 11:07 |
royalty |
or getById(int $id) |
| # |
Apr 19th 2019, 11:07 |
royalty |
getByWhatever(string $param) |
| # |
Apr 19th 2019, 11:07 |
royalty |
like |
| # |
Apr 19th 2019, 11:07 |
royalty |
asdfgh, it's better to define your own findBy queries |
| # |
Apr 19th 2019, 11:06 |
asdfgh |
i have tried to add cache() but it is not recognized |
| # |
Apr 19th 2019, 11:06 |
asdfgh |
ricks it seems that we cannot use cache() for findBy... queries |
| # |
Apr 19th 2019, 11:05 |
ricksaccous |
it might work without using TableRegistry |
| # |
Apr 19th 2019, 11:05 |
ricksaccous |
so if you want to try again with tableLocator |
| # |
Apr 19th 2019, 11:04 |
asdfgh |
yes correct |
| # |
Apr 19th 2019, 11:03 |
ricksaccous |
you'd have to do TableLocator->get(); |
| # |
Apr 19th 2019, 11:03 |
ricksaccous |
the mistake you might be making is if you use TableLocator::get it won't work because the method is not static |
| # |
Apr 19th 2019, 11:03 |
asdfgh |
debug(TableRegistry::getTableLocator()->get("ActivityTypes")->findByActivity('view')->first()); |
| # |
Apr 19th 2019, 11:03 |
ricksaccous |
it seems that |