Having some length limit by default is a good idea - if you forget validation someone can enter megabytes/gigabytes into some unassuming post title, essentially breaking everything. Better have some protection by default
thousandsofthem
DidactMacros
benwilson512
Author of Craft GraphQL APIs in Elixir with Absinthe
DidactMacros
Thanks, @benwilson512. I actually meant as type speccing for manually defined migrations. What I’ve realised however is that using the command mix help phx.gen.schema, gives a list of the supported migration option keys:
• :integer
• :float
• :decimal
• :boolean
• :map
• :string
• :array
• :references
• :text
• :date
• :time
• :time_usec
• :naive_datetime
• :naive_datetime_usec
• :utc_datetime
• :utc_datetime_usec
• :uuid
• :binary
• :enum
• :datetime - An alias for :naive_datetime
My understanding is that this list does not change depending on the adapter anyway.
I did read the initial OP as looking for a list like this though it seems that using fragments ultimately sufficed for him so I was a bit befuddled.
1
jswanner
Keep in mind that there are two separate things at play here (but ultimately related): in the migration you are specifying the type for the column of the database table, in the schema you are specifying the Elixir type to use in the struct.
2
garrison
As I said in my reply, you can pass any atom to the migration and it will be sent to the DB verbatim. For example mix phx.gen.auth uses a :citext column, which is of course not on the list (and comes from an extension).
0
DidactMacros
Yes I understand, that is what the OP was talking about as I understand it.
There is a schema fields list, but he could not find a migrations field list.
0