Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 41457200C72 for ; Fri, 12 May 2017 11:37:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3FD6F160BC8; Fri, 12 May 2017 09:37:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 83D48160BA3 for ; Fri, 12 May 2017 11:37:10 +0200 (CEST) Received: (qmail 90695 invoked by uid 500); 12 May 2017 09:37:07 -0000 Mailing-List: contact dev-help@fineract.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fineract.apache.org Delivered-To: mailing list dev@fineract.apache.org Received: (qmail 90680 invoked by uid 99); 12 May 2017 09:37:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 May 2017 09:37:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 37222185E70 for ; Fri, 12 May 2017 09:37:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.855 X-Spam-Level: X-Spam-Status: No, score=0.855 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_REPLY=1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id UfqLEqkfpAOE for ; Fri, 12 May 2017 09:37:04 +0000 (UTC) Received: from mail-oi0-f48.google.com (mail-oi0-f48.google.com [209.85.218.48]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id E0CA85F5C4 for ; Fri, 12 May 2017 09:37:03 +0000 (UTC) Received: by mail-oi0-f48.google.com with SMTP id h4so59453630oib.3 for ; Fri, 12 May 2017 02:37:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=4dqevcuJaLTdd7AlzlS0QzcWn7nT0GMr72jvEaWHVvE=; b=KpM8OXiv5LeAhPwvIG5MJ1waEpFuNlP9AUqEECzN6m6hGN39zKxfSgXvr/3I4E7gde i3tMgSAwZxDTObhOSZXtGlabhe2gmbpmuhk9vxRYYncoC/OOM0sifcftCg1yZt3yTBS6 ivjw2Tq3fFKJkYKsTgTuZbeMeVce/pl4ta6qWxlXurUSzryTYk67DFlUUd+IpBA9uRrc oTrRQj2DcUe7YfR59ruu/EZDvYyMedWDv9spbqygAODqJHSQqmrW9BOKnYhNQ8AX7mSh 9umxLrWjJVaHf/RdZF6r4hEqyhsHDB2SpNXc5gYGnKu3lR0geX7SddMzWJNW9rz7Bn3I Jykw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=4dqevcuJaLTdd7AlzlS0QzcWn7nT0GMr72jvEaWHVvE=; b=B6hJ9fQZC+RpjuVkdOb5qWpqDba+/5ePi1PqbHFB2QkDj7QzvGWdvdqRNucib2nP4g 0NxTJbUZ711vYIVCM5dOyl2b32XB1Y/llcVAeS47M+hl2juheSFugvDsfQ150REXaTob ptbz1n+GyTVlmBlF6LK/4L/DPyYIWFY0qHq/GCaMudj0qai2Qi5k93BDi0As4y08BEaP A+aR3t7TN35yqf0ZR5v5bburiPZcsS2NckMsZixmg0GRDBuj0gpRxjYZ1JihqDZPILTp aADMk8PI5rP6Zg5WzPrr+oU96INQC9YXL76mqtjLNP5/P8fFMqdM193wAeG/WQxp2yvn S8hw== X-Gm-Message-State: AODbwcCqFF4SJC89PSfD5mObs/5EAPuzfpHflYz5j80/FM0l9uS0Ilb2 kqQwqGlP7sjui9ItD0yBIgH2mIPWwg== X-Received: by 10.157.63.143 with SMTP id r15mr1303869otc.89.1494581822494; Fri, 12 May 2017 02:37:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.80.134 with HTTP; Fri, 12 May 2017 02:36:42 -0700 (PDT) In-Reply-To: References: From: Usman Khaliq Date: Fri, 12 May 2017 09:36:42 +0000 Message-ID: Subject: Re: Best Case Practice for Managing SQL Migrations Numbering To: dev@fineract.apache.org Content-Type: multipart/alternative; boundary="001a11c0ab909e1bc3054f507287" archived-at: Fri, 12 May 2017 09:37:11 -0000 --001a11c0ab909e1bc3054f507287 Content-Type: text/plain; charset="UTF-8" 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 > 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 > > > > > > > > Sent with Mailtrack > > > 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 --001a11c0ab909e1bc3054f507287--