UUID for primary key?

Discord Q&A strapi-questions
1

I am about to deploy my first strapi instance for a production environment. I am kinda scratching my head since all import and transfer seem to wanna wipe the entire database. Does anybody know how to do content diffs so I can pull changes from the content team into the development database without wiping the whole database? I am trying to use the strapi-plugin-import-export-entries plugin but I am seeing all kinds of bugs when exchanging exports between different devs, especially concerning components. Is there any way to setup strapi so it uses UUID for primary key?

This topic has been created from a Discord post (1277890692814995456) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord

2

Not in v4 no, we are slowly making the switch and documents in Strapi 5 will use CUIDs

3

I use a UID field and assign the value in the beforeCreate lifecycle function

4

That won’t set it as the PK though

5

no, won’t but at least I will have a uuid on every entry. and UID adds an index on that table too

6

Also for components? I used the lifecycle function for my api elements but I can’t see a way to do it for component hierarchies on my page.

7

I don’t care if it is the PK in particular as long as it is on every item. I just thought is might be easier to change the PK type because then the export functionality would become mergeable instantly between database instances

8

lifecycles cannot be used with components. Strapi 5’s CUID are at the document level (components are nested under entries so they won’t have a CUID assigned to them I don’t believe): Documents | Strapi Documentation

9

I use dynamic components to compose pages, I have had some really bad problems trying to merge changes on the component hierarchies

10

We don’t generally advise using other environments for creating content

11

And that’s not a direction we will be moving towards anytime soon (if ever)

12

well, I want to, willing to donate time and expertise

13

It’s not something we plan on entertaining

14

Lower environments should be for testing code changes and how those merge with production content that’s what we are focusing on

15

I look forward to having that discussion

16

the Features coming in Strapi 5 will further cement that production should be used for drafting content, previewing that content, and when it’s ready publishing it

17

I worked for several content managemen and understand the complexities

18

I was a senior engineer for Tridion content management system Tridion the Intelligent Content Platform (CMS & CCMS) - RWS

19

We have as well, that’s why we don’t plan on enabling it. Certainly you are free to do as you wish but please note that we don’t plan on adding native capabilities for what you are looking to do

20

I love strapi, great work!