I was working with absinthe for my new side project but i am getting primary key as null when i register the user but when i return all the users with another query i am getting the id as well. I have no idea how to fix this. This is my Absinthe Schema defmodule FlickrWeb.Schema do use Absinthe.S…

Is the ID returned when you run the create_new_user function in iex?

Seems to be the case. Here id is returned nil but id does not seem to be nil in my users table. [shell 1] [shell 2]

[rewriting my original response since it was originally poorly written] Looking things over, it looks like your database is generating the id value (which is fine, I do it that way myself). Assuming that is true, try Repo.insert(returning: true) rather than Repo.insert(). When you insert a value …

Thanks a lot. it’s working now. I just had a question though, i have used this same method for a couple of different projects as well and it worked and i never face any issues and i don’t know why it didn’t worked for this one. Do you have any idea what could be the real problem why it was not wor…

How are you generating your id’s, seems that you have disabled the option autogenerate? e.g. @primary_key {:id, :binary_id, autogenerate: true}

This is a very useful article to know about some unexpected id behaviour [image] Ecto UPSERT for different Primary Keys in Elixir Let's take a look into Ecto's implementation of PostgreSQL Upsert and how different types of primary keys could change the results of this command. Spoiler al…

As @hlx points out, somewhere along the way in your projects you likely have a difference in the autogenerate settings in this project vs. your other projects. In your other projects where you’re not returning: true, you may still have database table definitions that default the id to a generated U…

Just have this exactly above each schema ... statements in your project and you should be fine: @primary_key {:id, :binary_id, autogenerate: true} @foreign_key_type :binary_id schema "users" do # ... end

Just learned that PostgresSQL can auto-generate UUID primary key now. Does a UUID primary key serve any purpose other than avoiding conflict in case you scale to multiple databases?

In purpose the ID is somewhere public it avoids that the sequence is predictable. If you want to hide how many are already existing.

Getting Primary Key as NULL after creating a new user?

Questions & Help Questions

darnahsan October 5, 2022, 9:52am 9

This is a very useful article to know about some unexpected id behaviour