feat(customer): add migration file

[srindom]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 89ec9d0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
medusa-dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 25, 2024 4:29pm

3 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
api-reference	⬜️ Ignored (Inspect)			Jan 25, 2024 4:29pm
docs-ui	⬜️ Ignored (Inspect)	Visit Preview		Jan 25, 2024 4:29pm
medusa-docs	⬜️ Ignored (Inspect)	Visit Preview		Jan 25, 2024 4:29pm

[srindom]

@carlos-r-l-rodrigues redid the file please take another look

[carlos-r-l-rodrigues]

LGTM
It is just missing the create table customer if not exists.

[carlos-r-l-rodrigues]

Sorry, I just spotted a couple of other details.
customer_group table is also not being created if not exists, and we have to add the delete_at to it. (indexes created on this table also need the where delete_at is null)

All the tables involved in public methods exposed by the module will have to be "soft deletable", that way the workflows can restore it if needed.

[srindom]

Sorry, I just spotted a couple of other details.
customer_group table is also not being created if not exists, and we have to add the delete_at to it. (indexes created on this table also need the where delete_at is null)
All the tables involved in public methods exposed by the module will have to be "soft deletable", that way the workflows can restore it if needed.

@carlos-r-l-rodrigues - Is there something that needs to be done from a MikroORM perspective for this to work properly right now I just added it in the raw SQL?

[srindom]

Seems like it's only supported through custom expressions mikro-orm/mikro-orm#2837

So this should be sufficient right?

[carlos-r-l-rodrigues]

Seems like it's only supported through custom expressions mikro-orm/mikro-orm#2837

So this should be sufficient right?

Correct. if we want to auto generate that.
for the if [not] exists I haven't found anything