Pomelo.EntityFrameworkCore.MySql VS uulid.go

EntityFramework uses providers to translate Linq queries into real queries and connect to the datasource and convert the data into .net readable format. The MySQL provider for .NET is the official one but I think it has fallen on hard times and is not developed as much as before. You should probably look at Pomelo, which is a community library for .net core: https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql

For MySQL and friends you'll need the Pomelo data provider from https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql . Turns out there's an example of using the MySQL provider about halfway down that shows how to, but it is missing the '-o Model' parameter that you'd use to get your database model into a folder called Model.

This approach has become my preferred way of generating IDs for database rows. It is relatively space efficient and doesn't require a round trip to the database to generate an ID like auto increment does.

While working on a C# implementation for MySQL and we found that when the DB uses Little Endian Binary that the GUID must be reversed to store in order:

https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCo...

For those interested in time based UUIDs, I've written libraries in Ruby and Go to move quickly between them:

https://github.com/sudhirj/uulid.go

There’s a spec called ULID that’s pretty much this with default base32 encoding

https://github.com/ulid/spec

I’ve also worked on a UUID-ULID bridge for Go

https://github.com/sudhirj/uulid.go

And seeing as this is just 128 bits it’s quite easy to move seamlessly between formats and representations.

I’ve found this concept especially useful in nosql stores like DynamoDB, where using a ULID primary key makes objects time sortable automatically. It’s also quite easy to query for items by zeroing out the random component and setting only the time stamp bytes.