IMO, for any client specific functionality, start migration script with some big number (ex:7000), so that it won't conflict with any migration script added by Fineract community members.
Thanks, Nazeer On Fri, May 12, 2017 at 2:03 AM, Usman Khaliq <[email protected]> wrote: > Hi Guys, > We are creating a number of SQL migration scripts while building customised > functionalities for our clients. However, our concern is on what happens if > the migration number for scripts that we have used clashes with new > migration scripts uploaded in the main repo by the community. Is there a > best case practice that would be recommended here for numbering our > customized SQL migration scripts? > Thank you. > > -- > Kind Regards > Usman Khaliq > Programmer and R&D Lead > iDT Labs > 5 Foday Drive,Regent Road,Hill Station > Freetown,Sierra Leone > Tel: +92334 3777 059/ + 232 77 775 775 > Skype: usman.khaliq > Website:www.idtlabs.sl > > > > <https://mailtrack.io/> Sent with Mailtrack > <https://mailtrack.io/install?source=signature&lang=en&; > [email protected]&idSignature=22> >
