fineract-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Usman Khaliq <usman.khali...@gmail.com>
Subject Re: Best Case Practice for Managing SQL Migrations Numbering
Date Fri, 12 May 2017 09:36:42 GMT
Thanks Nazeer

On Fri, May 12, 2017 at 5:19 AM, Nazeer Shaik <
nazeer.shaik@confluxtechnologies.com> wrote:

> 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 <usman.khaliq91@gmail.com>
> 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&
> > referral=usman.khaliq91@gmail.com&idSignature=22>
> >
>



-- 
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 772 772
Skype: usman.khaliq
Website:www.idtlabs.sl

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message