Odd binary id mismatch

[peerreynders]

Just an aside; possibly relevant:

1:

MySQL does not support UUID types. Ecto emulates them by using binary(16).

2:

Because MySQL does not support RETURNING clauses in INSERT and UPDATE, it does not support the :read_after_writes option of Ecto.Schema.field/3.

3: TIL: Ecto reading after writes:

by default, Ecto doesn’t read data back from the database, after writing new or updated data.

@revati

mysql: 5.7.20

5.7.1 was released 2013-04-23. According to GUID/UUID Performance Breakthrough

This blog is mostly eliminated in MySQL 8.0

i.e. pre-8.0 UUIDs could be problematic/high maintenance.

See also:

MySQL PK using ordered UUID V1 with Ecto

Hey I have a few tables that need to have a UUID as the PK, and I would like to use a ordered V1 UUID. It seems that by default Ecto uses V4. What would be the best way to go about this. Create a new type that generates the UUIDV1 and swaps the parts about Create a new type that just wraps around a UUIDV1 to call my UuidBin() function in MySQL? Other? Or is there a setting I’ve missed somewhere that lets me set the value for a UUID field in Ecto? Thanks!

@jeremyjh

Can you please provide the actual schema definition and migration file?

+1