Hi Rajesh, Yes, cleanAll, cleanData or any other gradle target will only clean data when you are using embedded derby database as these targets are implemented to clean all DB data under directory runtime/data only. For all the other databases (mysql, postgresql etc) you need to manually drop the database.
Thanks and Regards, *Aditya Sharma* | Enterprise Software Engineer HotWax Systems <http://www.hotwaxsystems.com/> <https://www.linkedin.com/in/aditya-sharma-78291810a/> On Mon, Aug 28, 2017 at 9:36 AM, Rajesh Mallah <[email protected]> wrote: > Hi Jacques , > > is it true that cleanData only cleans embedded derby database ? > with remote postgresql server i feel it does not . > > regds > mallah. > > > On Sat, Aug 26, 2017 at 11:42 PM, Jacques Le Roux < > [email protected]> wrote: > > > Rajesh, > > > > Just FYI, you don't need to use > > > > rm -Rfv ./runtime/data # only for Derby database. > > > > ./gradlew cleanAll > > > > will do it anyway. It uses cleanData > > > > Jacques > > > > > > Le 26/08/2017 à 10:54, Rajesh Mallah a écrit : > > > >> my ../refresh.sh > >> > >> #!/bin/bash > >> rm -Rfv ./runtime/data # only for Derby database. > >> ./gradlew cleanAll > >> ./gradlew > >> ./gradlew "ofbiz --load-data readers=seed,seed-initial,demo" > >> # ./gradlew loadAdminUserLogin -PuserLoginId=admin > >> java -jar build/libs/ofbiz.jar > >> > >> > >> Note: the above does not use port-offset as my needs were different. > >> having a shell script files helps in iterating the create - test - > >> destroy > >> cycles. > >> > >> regds > >> mallah. > >> > >> > >> > >> On Sat, Aug 26, 2017 at 2:19 PM, Jacques Le Roux < > >> [email protected]> wrote: > >> > >> Sincerely Craig if it's for test, as suggested Rajesh it would be easier > >>> for you to use Derby with portoffset. Then tackle MySQL with > portoffset, > >>> hint each instance needs its set of DBs > >>> > >>> Jacques > >>> > >>> > >>> > >>> Le 26/08/2017 à 10:42, Craig Parker a écrit : > >>> > >>> <inline-jdbc > >>>> jdbc-driver="com.mysql.jdbc.Driver" > >>>> jdbc-uri="jdbc:mysql://127.0.0.1/ofbiz?autoReconnect=true"... > >>>> > >>>> > >>>> If I've created three new DBs, each with a test_ prefix (test_ofbiz, > >>>> test_ofbizolap, and test_ofbiztenant) has this got to say: ... > >>>> 127.0.0.1/test_ofbiz... in each of the three relevant datasource > >>>> sections? I've tried and failed, but just not sure yet if this is > what's > >>>> screwy, or something else. > >>>> > >>>> > >>>> On 08/26/2017 03:36 AM, Deepak Dixit wrote: > >>>> > >>>> Hi Craig, > >>>>> > >>>>> You can use portoffset feature > >>>>> Please reade README.md file for example > >>>>> > >>>>> Thanks & Regards > >>>>> -- > >>>>> Deepak Dixit > >>>>> www.hotwaxsystems.com > >>>>> www.hotwax.co > >>>>> > >>>>> On Sat, Aug 26, 2017 at 12:44 PM, Craig Parker <[email protected]> > >>>>> wrote: > >>>>> > >>>>> I've got OFBiz up and running on my Linux laptop with a MySQL > backend. > >>>>> Is > >>>>> > >>>>>> it possible to have another instance running somehow at the same > time > >>>>>> that > >>>>>> uses a different DB? Well, maybe three different DBs -- looks like > I'm > >>>>>> currently using ofbiz, ofbizolap, and ofbiztenant. > >>>>>> > >>>>>> What I'm aiming for is to have a "live" and a "play" area > eventually. > >>>>>> If I > >>>>>> want to go try something, I want to keep from breaking my install. > >>>>>> > >>>>>> Initially though, I want to have the default data in one, and the > >>>>>> other > >>>>>> a > >>>>>> blank slate. > >>>>>> > >>>>>> Right now the install is sitting in /ofbiz and being started up > with a > >>>>>> bash script via systemctl. I've not tried it yet, but I'm wondering > >>>>>> if > >>>>>> I > >>>>>> have to create the three new DBs, and duplicate what I have in > /ofbiz > >>>>>> to > >>>>>> something like /ofbiz-play, then create a similar startup script > that > >>>>>> fires > >>>>>> up things in that /ofbiz-play directory. > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>> > > >
