tag:jbilling.tenderapp.com,2012-10-15:/discussions/questions/1054-best-version-of-grail-for-jbilling-srcjBilling: Discussion 2018-10-19T08:10:38Ztag:jbilling.tenderapp.com,2012-10-15:Comment/417016012017-01-09T14:02:45Z2017-01-09T14:02:45ZBest version of Grail for Jbilling src<div><p>grails-2.4.3</p>
<p><em>Vikas Bodani</em> Mobile: +91-9828-605-495<br>
Web Data Technologies LLP, JAIPUR<br>
<a href="http://www.webdatatechnologies.in">www.webdatatechnologies.in</a>
| @WebDataConsult</p></div>vikas bodanitag:jbilling.tenderapp.com,2012-10-15:Comment/417016012017-01-09T14:11:05Z2017-01-09T14:11:07ZBest version of Grail for Jbilling src<div><p>Thanks vikas. that worked like a charm .<br>
i got another exception ..<br>
Error executing SQL INSERT INTO public.item_price (id, item_id,
currency_id, price, optlock) VALUES ((select_price p), 2.0, 1.0,
20.0, 1 ):ERROR: Duplicate key value violated Unique-Constraint
"item_price_pkey"</p>
<p>the auto migration cause this error . same DB works fine with
3.1 currently ..</p></div>junaid.khantag:jbilling.tenderapp.com,2012-10-15:Comment/417016012017-01-09T16:11:41Z2017-01-09T16:11:41ZBest version of Grail for Jbilling src<div><p>Appears to be a data issue. Duplicate value for the
item_price.id. You have<br>
to check the data that is being migrated to this db. May be its
test data<br>
and so your upgrade script has to be inspected.</p>
<p><em>Vikas Bodani</em> Mobile: +91-9828-605-495<br>
Web Data Technologies LLP, JAIPUR<br>
<a href="http://www.webdatatechnologies.in">www.webdatatechnologies.in</a>
| @WebDataConsult</p></div>vikas bodanitag:jbilling.tenderapp.com,2012-10-15:Comment/417016012017-01-09T16:49:45Z2017-01-09T16:49:47ZBest version of Grail for Jbilling src<div><p>i solved the data issue but still have some problems . i can not
grails run-app</p>
<p>can you please tell me the reason . logs are attached .
regards</p></div>junaid.khantag:jbilling.tenderapp.com,2012-10-15:Comment/417016012017-01-09T18:22:12Z2017-01-09T18:22:12ZBest version of Grail for Jbilling src<div><p>configure the db correctly. it may not be connecting to the
right db.</p>
<p><em>Vikas Bodani</em> Mobile: +91-9828-605-495<br>
Web Data Technologies LLP, JAIPUR<br>
<a href="http://www.webdatatechnologies.in">www.webdatatechnologies.in</a>
| @WebDataConsult</p></div>vikas bodanitag:jbilling.tenderapp.com,2012-10-15:Comment/417016012017-01-10T09:05:07Z2017-01-10T09:20:19ZBest version of Grail for Jbilling src<div><p>I am connected to database 3.1 . will it auto update for i have
to run some script ?<br>
i tried :</p>
<p>groovy UpdateDB.groovy</p>
<p>but i get this exception :<br>
No such property: includeTargets for class: UpgradeDb<br>
groovy.lang.MissingPropertyException: No such property:
includeTargets for class: UpgradeDb</p></div>junaid.khantag:jbilling.tenderapp.com,2012-10-15:Comment/417016012017-01-10T10:01:05Z2017-01-10T10:07:16ZBest version of Grail for Jbilling src<div><p>grails upgrade-db -user=**** pass=***-db=jbilling_test
-dbVersion=4.1 -url="jdbc:postgresql://****:5432/jbilling_test"
-schema jbilloing</p>
<p>causes this problem .<br>
Error Error executing script UpgradeDb: :
liquibase.exception.MigrationFailedException: Migration failed for
change set descriptors/database/jbilling-upgrade-4.1.xml::#11107 -
Line Percentage::Rohit Gupta: Reason:
liquibase.exception.DatabaseException: Error executing SQL ALTER
TABLE jbilling.order_change ADD is_percentage BOOLEAN NOT NULL
DEFAULT FALSE: ERROR: relation "jbilling.order_change" does not
exist (Use --stacktrace to see the full trace)</p></div>junaid.khan