Replies: 2 comments 1 reply
-
Any thoughts on this are greatly appreciated please. |
Beta Was this translation helpful? Give feedback.
0 replies
-
yes you can have composite primary keys. Also, stay tuned for 64-bit
snowflake sequences that are guaranteed to be unique on your cluster.
Snowflakes are faster to generate the UUID's and they only take upo
64bits rather than 128bits.
…On Wed, Nov 8, 2023 at 6:11 PM iamjrock ***@***.***> wrote:
Any thoughts on this are greatly appreciated please.
—
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMWOHVPHNGWB5TEXN7HRN3YDQGQLAVCNFSM6AAAAAA6T2E5B6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TKMJWGE4DC>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
iamjrock
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
pgEdge is awesome, thx team.
For Active-Active replication, I understand that I need a primary key on each table and that I cannot use sequences/auto-increment. So an UUID, ULID, etc.
But what about composite primary (UUID) keys?
Let's take the example of a many-to-many pivot table:
Beta Was this translation helpful? Give feedback.
All reactions