Hi,
On Fri, Jul 22, 2016 at 2:19 PM, Kishanthan Thangarajah wrote:
> "-Dsetup" is a development time option and in production it is not used
> mostly. Users manually populate the DB's using relevant scripts by
> executing them separately. Due to this fact only, we did not
"-Dsetup" is a development time option and in production it is not used
mostly. Users manually populate the DB's using relevant scripts by
executing them separately. Due to this fact only, we did not invest time in
supporting mysql 5.7 with "-Dsetup" option. We have documented this also :
Hi Pubudu,
As per the chat I had with Kalpa he has initially fixed Jira [1] to work
with -Dsetup. As a result of discussion [2] they have reverted the fix.
[1]. https://wso2.org/jira/browse/CARBON-15913
[2]. "WSO2 Carbon Kernel 4.4.6 throws exceptions when rinning Oracle DB
script"
Cheers!
Hi Pubudu,
When we tested API manager 1.10.0 - MySQL 5.7 compatibility for a customer
issue we fixed the MySQL scripts but we didn't give '-Dsetup' functionality
support rather delivered the working scripts.
In the current API manager 2.0.0 release, also we have working scripts for
MySQL 5.7
+1 to Nuwan's suggestion.
I too have experienced inconsistencies in the past while using the -Dsetup
when configuring the databases where we still have to manually execute the
scripts. Since we are not using this feature in production environments I
think it wouldn't hurt to get rid of this all
Practically the -Dsetup option is never used in production. All "real"
users of our products have DB admins and all that who carefully evaluate
and execute our DB scripts on their Database servers. They would never
allow a product startup process to create tables and indexes at will on
their
Hi all,
When we use MySql 5.7 as the DB and start the server with -Dsetup without
manually executing the scripts at DB level, we have observed the issue
logged at [1] while testing wso2esb-5.0.0-PRE-BETA2-PACK1.zip pack. The
reason behind this is, by default the pack is picking up mysql.sql