Matt Fulgo
Matt Fulgo
Good to know. I think that could be made explicit in the Scaladoc, and I'm guessing this is the case for other methods as well.
@smanikim - I'm not sure. Maybe try bringing it to the attention of a maintainer.
@hoffrocket - I figured it out, and it's not really a bug so much as a versioning and documentation issue. In 131b20e7, you added two new "put" methods to the...
On a related note, the two methods probably should have been named `putData` for consistency with `postData`.
> @malkaviano could you verify that the issue no longer occurs if the `serverTimezone` is configured in the jdbc url? I can confirm that setting `serverTimezone=UTC` resolved this for me....
In my use case, I have references in my `application.conf` that must be resolved with a custom `ConfigResolver`. Since this call to `.load()` ultimately uses `ConfigResolveOptions.default()`, without allowing me to...
> In your case the database has not been created by Slick and that is what is causing the mismatch. In my experience, that is often the case for production...
I'm able to reproduce the issue in `v1.10.2`, `v1.10.1`, `v1.10.0`, `v1.9.2`, `v1.9.1`, `v1.9.0`, `v1.8.2`, `v1.8.1`, `v1.8`, but not `v1.7.4`. @samuelcolvin - Given that this has been an issue since 2021-02-26,...
I'm just saying it's new as of v1.8, so it's been a bug for a while. I'm sure it's fixable in v1, just a question of effort and whether you...
#685 is tangentially related to this.