13 replies

builk_create upsert seems to be broken

Blibs · 2023-06-11T01:59:53.777Z

I have the following create in my resource: ```elixir create :create do description "Creates a new predefined school" primary? true accept [:name, :uid, :geography, :address, :city, :district, :state, :country, :type] upsert? true upsert_identity :unique_uid upsert_fields [:name, :geography, :address, :city, :district, :state, :country, :type] end ``` the `upsert_identity` comes from this identity: ```elixir identity :unique_uid, [:uid] ``` Just so you know, the `:uid` field is not a primary key. If I try to insert a row with the same `uid` as one that already exists in the DB using the create funciton, it works as expected and I get the `ON CONFLICT ("uid")` in the SQL query. Now, if I try to do the same, but with a `bulk_create` call, the resulti SQL query will contain `ON CONFLICT ("id")`, in other words, it uses `id` instead of `uid` which was set by the `upsert_identity` function.

I have the following create in my resource:

    create :create do
      description "Creates a new predefined school"

      primary? true

      accept [:name, :uid, :geography, :address, :city, :district, :state, :country, :type]

      upsert? true
      upsert_identity :unique_uid
      upsert_fields [:name, :geography, :address, :city, :district, :state, :country, :type]
    end

    create :create do
      description "Creates a new predefined school"

      primary? true

      accept [:name, :uid, :geography, :address, :city, :district, :state, :country, :type]

      upsert? true
      upsert_identity :unique_uid
      upsert_fields [:name, :geography, :address, :city, :district, :state, :country, :type]
    end

the

upsert_identity

upsert_identity

comes from this identity:

identity :unique_uid, [:uid]

identity :unique_uid, [:uid]

Just so you know, the

:uid

:uid

field is not a primary key.

If I try to insert a row with the same

uid

uid

as one that already exists in the DB using the create funciton, it works as expected and I get the

ON CONFLICT ("uid")

ON CONFLICT ("uid")

in the SQL query.

Now, if I try to do the same, but with a

bulk_create

bulk_create

call, the resulti SQL query will contain

ON CONFLICT ("id")

ON CONFLICT ("id")

, in other words, it uses

id

id

instead of

uid

uid

which was set by the

upsert_identity

upsert_identity

function.

Ash Framework•3y ago•

13 replies

Blibs

builk_create upsert seems to be broken

I have the following create in my resource:

    create :create do
      description "Creates a new predefined school"

      primary? true

      accept [:name, :uid, :geography, :address, :city, :district, :state, :country, :type]

      upsert? true
      upsert_identity :unique_uid
      upsert_fields [:name, :geography, :address, :city, :district, :state, :country, :type]
    end

    create :create do
      description "Creates a new predefined school"

      primary? true

      accept [:name, :uid, :geography, :address, :city, :district, :state, :country, :type]

      upsert? true
      upsert_identity :unique_uid
      upsert_fields [:name, :geography, :address, :city, :district, :state, :country, :type]
    end

the

upsert_identity

upsert_identity

comes from this identity:

identity :unique_uid, [:uid]

identity :unique_uid, [:uid]

Just so you know, the

:uid

:uid

field is not a primary key.

If I try to insert a row with the same

uid

uid

as one that already exists in the DB using the create funciton, it works as expected and I get the

ON CONFLICT ("uid")

ON CONFLICT ("uid")

in the SQL query.

Now, if I try to do the same, but with a

bulk_create

bulk_create

call, the resulti SQL query will contain

ON CONFLICT ("id")

ON CONFLICT ("id")

, in other words, it uses

id

id

instead of

uid

uid

which was set by the

upsert_identity

upsert_identity

function.

builk_create upsert seems to be broken

Similar Threads

builk_create upsert seems to be broken

Similar Threads

Similar Threads

Similar Threads