Open jurgispods opened 5 years ago
The issue seems to be here. There is no case for LocalDateTime
, only for OffsetDateTime
, Instant
and Duration
.
If I modify my table definition to use a columns type of Instant
instead of LocalDateTime
, it works as expected. Is this a bug or am I missing some implicit conversions that need to be included?
Your profile merged both PgDateSupport
and PgDate2Support
, so you need use specific *Implicit
names.
DateTimeImplicits
is an alias for both Date2DateTimeImplicitsDuration
and SimpleDateTimeImplicits
.
I'm sorry, but I don't get what I have to change in my code. Can you tell me the specific traits I need to extend
PostgresProfile
MyAPI
in order to be able to read values as instances of LocalDateTime
?
...
override val api = new MyAPI{}
trait MyAPI extends super.API
with JsonImplicits
//with SimpleDateTimeImplicits
with DateTimeImplicits
{
...
Here, you should use SimpleDateTimeImplicits
and/or Date2DateTimeImplicitsDuration
instead of DateTimeImplicits
.
Hi. First of all thank you for providing this great library which helped me a lot so far, especially when dealing with Postgres JSONB columns.
I recently added a
LocalDateTime
column to my table and I was able to write to the table without any problems. However, when reading back the table from another application - using the same profile and table definition - I get the following weird error:This is my table definition:
These are my mapped case classes:
And this is my Postgres profile:
I am using
slick-pg
version 0.16.3 together with PostgreSQL version 10.4.Any idea what is going wrong here?