| # |
Jun 11th 2018, 13:34 |
 dereuromark |
also less change of conflict with table method names, past or future |
| # |
Jun 11th 2018, 13:34 |
dereuromark |
more creative method names are usually the best thing |
| # |
Jun 11th 2018, 13:34 |
josbeir |
bleh @ trait method aliasses :see_no_evil: |
| # |
Jun 11th 2018, 13:32 |
dereuromark |
but fair enough |
| # |
Jun 11th 2018, 13:32 |
dereuromark |
IDE and phpstan might not be happy here though |
| # |
Jun 11th 2018, 13:32 |
dereuromark |
True, that might work :slightly_smiling_face: |
| # |
Jun 11th 2018, 13:31 |
admad |
to alias the method |
| # |
Jun 11th 2018, 13:31 |
admad |
oh i misread. you should infact you "implementedMethods" option of behavior |
| # |
Jun 11th 2018, 13:28 |
admad |
@tiagoab you'll have to alias on of the trait's method. `use FooTrait { bar as baz }` or something like that |
| # |
Jun 11th 2018, 13:26 |
dereuromark |
Technically you are very limited here. |
| # |
Jun 11th 2018, 13:26 |
dereuromark |
Maybe use a more unique name then. |
| # |
Jun 11th 2018, 13:26 |
dereuromark |
Sounds like overuse of trait pattern |
| # |
Jun 11th 2018, 13:26 |
tiagoab |
I got a trait T that implements a method; In two custom behaviors (A and B), I want to use method's trait . When I use both behaviors in a table, this cause a duplicate method error. How can I resolve it? |
| # |
Jun 11th 2018, 13:25 |
neon1024 |
However you make them, they remain the same. |
| # |
Jun 11th 2018, 13:25 |
dereuromark |
Experience :slightly_smiling_face: |
| # |
Jun 11th 2018, 13:25 |
neon1024 |
You’re making too many assumptions @dereuromark |
| # |
Jun 11th 2018, 13:25 |
dereuromark |
not acceptable in my book :slightly_smiling_face: at least not without clearly saying that this is not useful to do. |
| # |
Jun 11th 2018, 13:24 |
dereuromark |
bugs |
| # |
Jun 11th 2018, 13:24 |
dereuromark |
@neon1024 Allowing this hack only makes him complain a few days or weeks about tons of follow up bucks (e.g. bake, other tools breaking now) |
| # |
Jun 11th 2018, 13:23 |
admad |
veve: you have been provided solution to your problem, no point continuing a non productive discussion :slightly_smiling_face: |
| # |
Jun 11th 2018, 13:23 |
dereuromark |
@neon1024 He is desprectful in accepting experienced advice - this is clarification. |
| # |
Jun 11th 2018, 13:23 |
lorenzo |
veve here’s an example https://book.cakephp.org/3.0/en/orm/saving-data.html#saving-complex-types |
| # |
Jun 11th 2018, 13:22 |
dereuromark |
nano opt has nothing do with the computer size |
| # |
Jun 11th 2018, 13:22 |
lorenzo |
use the `_initializeSchema()` function in your tables to change the type of the columns you need to be different |
| # |
Jun 11th 2018, 13:22 |
veve |
a good dev is able to work on very small computers and is not insulting towards others |
| # |
Jun 11th 2018, 13:22 |
neon1024 |
Also not nice to talk down to people @dereuromark |
| # |
Jun 11th 2018, 13:22 |
lorenzo |
veve, there is a way to do it |
| # |
Jun 11th 2018, 13:21 |
dereuromark |
:slightly_smiling_face: Moving on |
| # |
Jun 11th 2018, 13:21 |
dereuromark |
A good dev, however, knows when to use good advice given, instead of just disagreeing even though he doesnt have the numbers and facts to prove it. |
| # |
Jun 11th 2018, 13:21 |
admad |
veve: if you want to be pig headed about it then you can override the column type by modifying table schema from Table::__initializeSchema() method https://api.cakephp.org/3.6/class-Cake.ORM.Table.html#__initializeSchema |
| # |
Jun 11th 2018, 13:21 |
veve |
no way to talk ! :-( |
| # |
Jun 11th 2018, 13:20 |
dereuromark |
what do you is up to you. |
| # |
Jun 11th 2018, 13:20 |
dereuromark |
I dont care :slightly_smiling_face: Just saying what the correct way is, based also on hundreds of years of experience of the top 10+ core devs. |
| # |
Jun 11th 2018, 13:20 |
dereuromark |
even unsigned etc is usually totally irrelevant, but if you want to you can do it |
| # |
Jun 11th 2018, 13:20 |
veve |
I'm sorry but I completly disagree with you. |
| # |
Jun 11th 2018, 13:19 |
neon1024 |
madrid988, If a “semi-month” is indeed a fortnight, I wrote a bit of code for working with that which could be helpful, https://github.com/davidyell/Fortnights |
| # |
Jun 11th 2018, 13:19 |
dereuromark |
yes, thats tinyint(2) |
| # |
Jun 11th 2018, 13:16 |
josbeir |
i can aslo concur :slightly_smiling_face: |
| # |
Jun 11th 2018, 13:16 |
veve |
I have fields with 3 ou 4 states maximum, so no need to oversize the fields |
| # |
Jun 11th 2018, 13:15 |
dereuromark |
ask lorenzo and others who actually work with huge DBs with cake :slightly_smiling_face: they can give you the numbers |
| # |
Jun 11th 2018, 13:15 |
dereuromark |
you only create huge bugs, the benefit is 0 here. |