Log message #4203660

# At Username Text
# Sep 17th 2019, 17:16 birdy247 yes
# Sep 17th 2019, 17:16 ricksaccous @birdy247 phinx?
# Sep 17th 2019, 17:15 birdy247 use $table->drop
# Sep 17th 2019, 17:14 birdy247 but the table is still there
# Sep 17th 2019, 17:14 birdy247 It says that it has worked
# Sep 17th 2019, 17:14 birdy247 I am trying to drop a table
# Sep 17th 2019, 16:57 daniel.upshaw Thank you @ndm
# Sep 17th 2019, 16:56 this.impetus @ndm thanks for replying, I started reading about error handling with cake, I underestimated how much there was to read, I should have done that before asking my question; I may be back lol
# Sep 17th 2019, 16:54 ndm @this.impetus No
# Sep 17th 2019, 16:52 ndm @daniel.upshaw Middlewares are invoked in the order in which they've been added. The error handler middleware wraps all following middlewares in a `try...catch`, so it's the other way around, stuff that happens before that wouldn't be processed by that handler. There's another error handler though, the one that is by default registered in `config/bootstrap.php`, it will handle errors until the middleware is registered.
# Sep 17th 2019, 16:46 this.impetus or obviate, maybe is a better word
# Sep 17th 2019, 16:45 this.impetus ... does cake somehow prevent the use of try..catch statements in controllers?
# Sep 17th 2019, 16:43 daniel.upshaw When it comes to Middleware, what are the implications of the order they are added to the queue? For example, if you add `ErrorHandlerMiddleware` before Authentication, does that mean that errors in the authentication process won't be handled? Or is that what you would want?
# Sep 17th 2019, 16:00 neon1024 :crossed_fingers:
# Sep 17th 2019, 16:00 neon1024 ..and maybe put the migration in a branch
# Sep 17th 2019, 16:00 neon1024 Take those database backups first
# Sep 17th 2019, 15:59 jotpe Thanks :slightly_smiling_face:
# Sep 17th 2019, 15:59 jotpe I guess I'll write a alter table and convert the entities then.
# Sep 17th 2019, 15:58 jotpe I live risky by default 8)
# 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: