umbrella VS Pomelo.EntityFrameworkCore.MySql

OP here. This project is implemented in Typescript and Svelte, with support from the thi.ng libraries.

This a is a really wide field. Basically its starts with one of the standard algorithms, like and l-system, a voronoi diagram, or simple combination of sin and cos to draw shapes. Have a look at thi-ng[1], just as example for a library that has implemented a lot of this kind of algorithms. The next step in my process is to think about how to destroy this forms as most of them are used a lot in this field and become boring. Using perlin noise as input to arguments of the algorithms is one way to do this. The other part is to make most all of the input variables easily changeable as most of the time the whole process is like writing the program and then spend a lot of time adapt the parameters until you get some interesting output. So in the end I have a small Svelte app, using Svelte only cause the data binding for the inputs so simple, which has tons of sliders that renders an SVG that can be saved in the end.

[1]https://github.com/thi-ng/umbrella

@thi.ng/ksuid https://github.com/thi-ng/umbrella/tree/develop/packages/ksu...

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...