pg-ulid
Dapper
Our great sponsors
pg-ulid | Dapper | |
---|---|---|
2 | 40 | |
58 | 17,128 | |
- | 1.1% | |
0.0 | 8.0 | |
over 4 years ago | 14 days ago | |
C | C# | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pg-ulid
-
Lesser Known PostgreSQL Features
Here's one[1], not actively maintained though.
[1] https://github.com/edoceo/pg-ulid
-
PostgreSQL UUID vs. Serial vs. Identity
Yeah, just use a UUID unless the bits to store the UUID really are your driving limitation (they're not), having a UUID that is non-linear is almost always the most straight-forward option for identifying things, for the tradeoff of human readability (though you can get some of that back with prefixes and some other schemes). I'm not going to rehash the benefits that people have brought up for UUIDs, but they're in this thread. At this point what I'm concerned about is just... what is the best kind of UUID to use -- I've recently started using mostly v1 because time relationship is important to me (despite the unfortunate order issues) and v6[0] isn't quite so spread yet. Here's a list of other approaches out there worth looking at
- isntauuid[1] (mentioned in this thread, I've given it a name here)
- timeflake[2]
- HiLo[3][4]
- ulid[5]
- ksuid[6] (made popular by segment.io)
- v1-v6 UUIDs (the ones we all know and some love)
- sequential interval based UUIDs in Postgres[7]
Just add a UUID -- this almost surely isn't going to be what bricks your architecture unless you have some crazy high write use case like time series or IoT or something maybe.
[0]: http://gh.peabody.io/uuidv6/
[1]: https://instagram-engineering.com/sharding-ids-at-instagram-...
[2]: https://github.com/anthonynsimon/timeflake
[3]: https://en.wikipedia.org/wiki/Hi/Lo_algorithm
[4]: https://www.npgsql.org/efcore/modeling/generated-properties....
[5]: https://github.com/edoceo/pg-ulid
[6]: https://github.com/segmentio/ksuid
[7]: https://www.2ndquadrant.com/en/blog/sequential-uuid-generato...
Dapper
-
Working with Dapper/SQL-Server Framework 4.8 C#
In both samples to get all records and to get a single record works fine but there is a better way to perform the same work using NuGet package Dapper. Dapper is extremely easy to use and built with performance in mind. In the source code provided the basic operations are covered, to take things to the next level and read the information at GitHub, the following page and other code samples in the following repository.
-
Working with Dapper in C#
In this article learn how to use Dapper an open-source object-relational mapping (ORM) library for .NET and .NET Core applications. Unlike many articles out there, this one will provide source code to try everything out that is shown in an easy-to-follow way by beginning with a single table then in part two of this series will work with multiple tables.
- Interceptors (new C# metaprogramming feature) to fuel DapperAOT development
- API REST C# Entity Framework y SQL
-
Integration Testing Postgres Store
Dapper
-
REST API using C# .NET 7 with MySql
I will be using Dapper - a simple object mapper for .Net along with MySqlConnector.
-
Resources for learning minimal API using dapper in .net
Maybe the more basic approach to dapper is their documentation https://github.com/DapperLib/Dapper the readme but again most likely you not gonna understand
-
SQL Connection Question
I think EF Core & EF are the successors to LINQ to SQL that you'd wanna look into, and/or Dapper if you wanna go lower.
-
Dapper is die?
The main maintainers of Dapper no longer work at Stack, but they're active enough to comment on recent pull requests: https://github.com/DapperLib/Dapper/pull/1887.
-
Is MSSQL Server the easiest sql database to integrate with a C# .NET application?
MarieDB and dapper https://github.com/DapperLib/Dapper
What are some alternatives?
ksuid - K-Sortable Globally Unique IDs
efcore-dapper-benchmark - A project that I have created to benchmark the read/write performance of EFCore vs Dapper
cuid - Collision-resistant ids optimized for horizontal scaling and performance.
Npgsql - Npgsql is the .NET data provider for PostgreSQL.
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
PetaPoco - Official PetaPoco, A tiny ORM-ish thing for your POCO's
tbls - tbls is a CI-Friendly tool for document a database, written in Go.
Knex - A query builder for PostgreSQL, MySQL, CockroachDB, SQL Server, SQLite3 and Oracle, designed to be flexible, portable, and fun to use.
timeflake - Timeflake is a 128-bit, roughly-ordered, URL-safe UUID.
postgres-elasticsearch-fdw - Postgres to Elastic Search Foreign Data Wrapper
LINQ to DB - Linq to database provider.