I'm Ok to enhance the documentation, but, we don't really need to use / as
the terminator in migration scripts as they are supposed to run manually.
On Tue, May 9, 2017 at 12:22 PM, Rajith Roshan wrote:
> Hi,
>
> Yeah I think we can agree with maduranga. AFAIK this only happens with
> db2. Becau
Hi,
Yeah I think we can agree with maduranga. AFAIK this only happens with db2.
Because its default delimiter is ;. Other dbscripts get executed when we
run them against the database. Its better to update the docs in order to
provide guidance saying that delimiter we have used in our db scripts ar
Hi Abimaran,
Usually if we start the pack with -Dsetup option product database scripts
are run through [1] to create databases which specifically checks for "/"
to identify a single query for DB2. So product database scripts has "/" as
the statement terminator. Anyway this terminator will not be t
Hi Ishara,
Any reason for having / as the statement terminator in DB2 script? The
default DB2 statement terminator is ;
API Manager had the same issue and we fixed it.
[1] :
https://www.ibm.com/support/knowledgecenter/SS62YD_2.2.1/com.ibm.datatools.sqlxeditor.doc/topics/tchngstmtterm.html
[2] :
Thanks Rajith for finding out this.
@Dinali Can you please update the scripts.
-Ishara
On Fri, May 5, 2017 at 11:52 PM, Rajith Roshan wrote:
> The migration resources for db2 specified in step 11 of doc [1] is giving
> errors. It tries to insert boolean values to columns which have type
> smal
