Migration sequence not available

[mnadeemasghar]

I have a problem here while using the the package.

Senario:

If we have two table users and hotels, here hotels is owned by users via owner_id.

Problem:

By running the php artisan migrate:sync it creates hotels table first, which leads to migration error because hotels have foreign key owner_id linked to users

Required Solution:

Somehow, add sequence of the migrations.

[abdumu]

what happened? why it got closed quickly Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: M Nadeem Asghar ***@***.***> Sent: Thursday, November 14, 2024 12:43:56 PM To: awssat/laravel-sync-migration ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [awssat/laravel-sync-migration] Migration sequence not available (Issue #21) Closed #21<#21> as not planned. — Reply to this email directly, view it on GitHub<#21 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAA4A2VDAKVY3XKNLKJUAT32ARWFZAVCNFSM6AAAAABRYOUCVGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGI4TKNJZHAZDMNY>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[BSN4]

@abdumu this issue related to foreign keys its known issue at least for me ...

[abdumu]

interesting… 🤔 we can’t implement this? Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: Bader ***@***.***> Sent: Friday, November 15, 2024 11:25:35 PM To: awssat/laravel-sync-migration ***@***.***> Cc: Abdulrahman ☕️ ***@***.***>; Mention ***@***.***> Subject: Re: [awssat/laravel-sync-migration] Migration sequence not available (Issue #21) @abdumu<https://github.com/abdumu> this issue related to foreign keys its known issue at least for me ... — Reply to this email directly, view it on GitHub<#21 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAA4A2S4JMAVVUPPJTNEEZ32AZKD7AVCNFSM6AAAAABRYOUCVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZHA3DAMBXG4>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[BSN4]

@abdumu I can't think of easy fix honestly I think this my fault I thought devs will figure it out

[mnadeemasghar]

The issue was mistakenly added in wrong repo 🤣 but still relevant here. It's good luck in coding. 😄
reopening it now.