I am not sure of the way You set your constraints. There is a post here describing the process
I think You should have a unique index on multiple fields in the migration, then use only one constraint.
But it does not explain why it works for number_input and not for multiple select.
For this, I would add
IO.inspect(params)
to the create action of your controller, just to check what You receive as input…
I’m sorry, I’m unfamiliar with IO.inspect, I did google for a while and inserted into the create action, but I don’t know where should I see the output, also I’m thinking I should just remake the table with belongs_to and has_many and avoid using :id_medico as an attribute name.
The medics table is now plural, but what is the name of your Schema? Medic or Medics?
The schema is usually singular, and it can cause some trouble, in particular the way you will name association. You will use singular for has_one, belongs_to but plural for has_many, many_to_many
As I see your key, I guess You have defined a Medics schema, as a plural form.
IO.inspect logs to the running console, where You started the server…
This should be the output:
[debug] Processing with MedicaWeb.AppointmentController.create/2
Parameters: %{"_csrf_token" => "NTwBMhoPAzsdXTEuFy47PVYBIDpyJgAADZbcHm2xp7kbzmZV/uZcBQ==", "_utf8" => "✓", "appointment" => %{"bloque" => "1", "descripcion" => "1", "fecha" => "2018-06-06", "id_medico" => "1", "rut_paciente" => "19386399-K"}}
Pipelines: [:browser]
%{
"bloque" => "1",
"descripcion" => "1",
"fecha" => "2018-06-06",
"id_medico" => "1",
"rut_paciente" => "19386399-K"
}
If the module is called Medic, then there is something wrong…
It should never have requested for medics_id, but for medic_id.
And appointment should belongs_to medic (singular!) with medic_id as the key of this association.
If You have something belongs_to a user, the key will be user_id, and not users_id.
So I guess this sentence should be wrong?
mix phx.gen.html Clinic Medic medics nombre:string apellido:string especialidad:string
This command looks fine, but this message sure does not
Hmm, for some reason now I get:
ERROR 42703 (undefined_column): column a0.medics_id does not exist
In index.
Do You have this line in appointment?
belongs_to :medic, Clinic.Medic
Yes, tried with both medic and medics, medic returns (with Clinic.Medic):
ERROR 42703 (undefined_column): column a0.medic_id does not exist,
could it be because I used id_medico as an attribute (I removed it in appointment).