[Best practice] Should I add a version to my json schemas for future changes?

[Extarys]

I read that it is prefered to add a version number to the jsonb data to represent which schema we are using. Is this a good practice with this extention? I'm looking for best practice for future migrations and all but I couldn't find much informations other than an old blog post about Json in RDBMS

Not an issue per se but quite important so users don't regret later down the road I guess :P

export {};
declare global {
	namespace PrismaJson {
		// you can use typical basic types
		type MyType = boolean;
		// or you can use classes, interfaces, object types, etc.
		export type MyJsonV1 = {
			schemaV: number;
			foo: string;
			bar: number;
		}
	}

}

[arthurfiorette]

I think using the typename as version a bad practice in general. I'd just use it as normally, and when I'll need to change, change the type to a union and handle the migration case or even just rename the type so your migration work can be done inside a prisma migration file.

[Extarys]

Thank you for sharing your wisdom, and sorry I didn't see the Discussions tab there 🤦

[arthurfiorette]

No problem:)