| # |
Sep 17th 2019, 15:58 |
 neon1024 |
Although kinda dangerous to destroy data in an automated process :face_palm: |
| # |
Sep 17th 2019, 15:57 |
neon1024 |
At least then, you could also rollback neatly by converting your date time back to date with ``conference_begin` = DATE(conference_begin)` |
| # |
Sep 17th 2019, 15:57 |
neon1024 |
Perhaps you need to write `up()` and `down()` methods with your own `ALTER TABLE..` |
| # |
Sep 17th 2019, 15:56 |
neon1024 |
Strange :thinking_face: |
| # |
Sep 17th 2019, 15:56 |
jotpe |
yep |
| # |
Sep 17th 2019, 15:56 |
neon1024 |
..and the existing column is `DATE` ? |
| # |
Sep 17th 2019, 15:55 |
jotpe |
->changeColumn('conference_begin', 'datetime') |
| # |
Sep 17th 2019, 15:54 |
neon1024 |
As you’re adding a time, it should be okay for existing data I’d think. Just your new times will all be `00:00:00` |
| # |
Sep 17th 2019, 15:54 |
jotpe |
Yes, but the migrations command throws this |
| # |
Sep 17th 2019, 15:54 |
neon1024 |
Isn’t that `changeColumn()` ? |
| # |
Sep 17th 2019, 15:53 |
jotpe |
And got `Warning: 1265 Data truncated for columnand got ` |
| # |
Sep 17th 2019, 15:52 |
jotpe |
I have existing data |
| # |
Sep 17th 2019, 15:52 |
jotpe |
Is there any way to convert a mysql _date_ field to _datetime_ with migrations? |
| # |
Sep 17th 2019, 15:50 |
jotpe |
;) |
| # |
Sep 17th 2019, 15:49 |
admad |
Haha.. even Trump wouldn't be that naive |
| # |
Sep 17th 2019, 15:48 |
jotpe |
Hope the best for you ;) |
| # |
Sep 17th 2019, 15:48 |
neon1024 |
Although @admad does raise a good point as `en_US` wouldn’t match with `Europe/London` timezone |
| # |
Sep 17th 2019, 15:46 |
neon1024 |
Careful @admad or they’ll “bring democracy” your way ;) |
| # |
Sep 17th 2019, 15:46 |
admad |
Surely the Americas can understand "colour" instead of "color" :P |
| # |
Sep 17th 2019, 15:45 |
admad |
@spriz wouldn't doing en_GB make more sense for a Europe based site? |
| # |
Sep 17th 2019, 15:21 |
jotpe |
Nice, thanks @spriz |
| # |
Sep 17th 2019, 15:11 |
neon1024 |
Sure sounds like a good plan :thumbsup: |
| # |
Sep 17th 2019, 15:08 |
spriz |
should I make my own `CustomDecimalType` and enable the locale parser, and use that one in `_initializeSchema()` ? |
| # |
Sep 17th 2019, 15:07 |
spriz |
I would like to use only the `localeParser` features of `DecimalType` in 1 table at a time - what is the best approach here? |
| # |
Sep 17th 2019, 15:05 |
ricksaccous |
with a vision |
| # |
Sep 17th 2019, 15:05 |
ricksaccous |
the man with a Vue |
| # |
Sep 17th 2019, 15:03 |
spriz |
if one wants to tinker with frontend |
| # |
Sep 17th 2019, 15:02 |
spriz |
Uh, nice :) |
| # |
Sep 17th 2019, 15:02 |
neon1024 |
Doing Vue.js this week :slightly_smiling_face: |
| # |
Sep 17th 2019, 15:02 |
spriz |
in case anyone stumbles upon it: https://gist.github.com/Spriz/9a328c0392ce7dfa674e07ceda7ceb12 |
| # |
Sep 17th 2019, 15:02 |
neon1024 |
Although I’m mostly on internal tooling these days |
| # |
Sep 17th 2019, 15:01 |
neon1024 |
I’ve done one site so far and it was quite a fun challenge |
| # |
Sep 17th 2019, 15:01 |
neon1024 |
We’re fully Brexit and don’t do any multi-lingual sites :face_palm: |
| # |
Sep 17th 2019, 15:01 |
spriz |
but adding `en_GB` is a matter of adding a `.po` file and adding the record to our bootstrap.php :P |
| # |
Sep 17th 2019, 15:00 |
spriz |
only `da_DK`, `en_US`, and `de_DE` |
| # |
Sep 17th 2019, 15:00 |
neon1024 |
Noice! |
| # |
Sep 17th 2019, 15:00 |
spriz |
we don't currently :) |
| # |
Sep 17th 2019, 15:00 |
neon1024 |
Oh, how do you select beween en_GB and en_US? |
| # |
Sep 17th 2019, 15:00 |
spriz |
or welp, we do it in a Middleware |
| # |
Sep 17th 2019, 14:59 |
spriz |
depending on the user's selected language |
| # |
Sep 17th 2019, 14:59 |
spriz |
we do that :) |