Closed phereford closed 6 years ago
I figured it out! Ecto has on by default read_after_writes: true
option for the primary key of an Ecto.Schema.
This removed that error:
@primary_key {:id, :integer, read_after_writes: false}
@phereford Good to know, I wasn't familiar with that option.
In general you want to generate ids on the client side with Redshift because of the lack of RETURNING
support which Ecto
adds to queries implicitly if the id would be generated by the db.
Hi there! Thank you for your work on this gem.
I am experiencing an issue. Here is my stack trace:
Here is the code I am using to invoke it:
What am I doing wrong here? Any advice is appreciated. Thanks!