Quantcast
Channel: Liquibase Forums
Viewing all 1169 articles
Browse latest View live
↧

Cannot find database driver for Redshift

November 20, 2017, 4:03 pm
$
0
0
Trying to run the following command

java -jar scripts/liquibase-core-3.3.3.jar 

                  --username=root

                 --password="myfakepassword" 

                  --url=jdbc:redshift://<redshift_path>.amazonaws.com:5439/dev

          --changeLogFile=scripts/master.xml

                  --driver=lib/liquibase-redshift-1.0-SNAPSHOT.jar 

                  --classpath=lib/liquibase-redshift-1.0-SNAPSHOT.jar 

                  update


Getting error


 Unexpected error running Liquibase: java.lang.RuntimeException: Cannot find database driver: lib/liquibase-redshift-1.0-SNAPSHOT.jar


I tried multiple options under https://github.com/liquibase/liquibase-redshift/releases but did not work . All of them give the same error. 


Is there something obvious I am missing?                        

↧
Search

Re : Cannot find database driver for Redshift

November 21, 2017, 2:34 am
$
0
0
I haven't tried it, but usually you use the driver property to point to a JDBC driver class and not a jar containing it.
As the redshift repository does not contain such a class i would probably just try without the "--driver" switch and just put the liquibase-redshift.jar in the same folder as liquibase.jar (maybe the classpath is enough, but I'm not sure about that).

kind regards
Daniel
↧
↧

Does liquibase support PostgreSQL 10?

November 26, 2017, 9:34 am
$
0
0
Hi,

Does liquibase 3.5 support support PostgreSQL 10?

mvn liquibase:generateChangeLog fails to generate the initial changelog.

liquibase.properties:
  1. url=jdbc:postgresql://localhost:5432/testdb
  2. driver=org.postgresql.Driver
  3. username=user
  4. password=pass

Error message:
  1. [ERROR] Failed to execute goal org.liquibase:liquibase-maven-plugin:3.5.3:generateChangeLog (default-cli) on project test-project: Error setting up or running Liquibase: liquibase.command.CommandExecutionException: liquibase.exception.DatabaseException: Error getting jdbc:postgresql://localhost:5432/testdb view with liquibase.statement.core.GetViewDefinitionStatement@fe34b86: Expected single row from liquibase.statement.core.GetViewDefinitionStatement@26bbe604 but got 0: Empty result set, expected one row -> [Help 1]

Database query and response:
  1. ERROR:  column i.indproc does not exist at character 610
  2. HINT:  Perhaps you meant to reference the column "i.indpred".

  4. SELECT NULL AS TABLE_CAT, NULL AS TABLE_SCHEM,  ct.relname AS TABLE_NAME, NOT i.indisunique AS NON_UNIQUE, NULL AS INDEX_QUALIFIER, ci.relname AS INDEX_NAME,  CASE i.indisclustered  WHEN true THEN 1 ELSE CASE am.amname  WHEN 'hash' THEN 2 ELSE 3 END  END AS TYPE,  a.attnum AS ORDINAL_POSITION,  CASE i.indpred WHEN 0 THEN a.attname ELSE ip.proname || '(' || ai.attname || ')' END AS COLUMN_NAME,  NULL AS ASC_OR_DESC,  ci.reltuples AS CARDINALITY,  ci.relpages AS PAGES,  NULL AS FILTER_CONDITION  FROM pg_class ct, pg_class ci, pg_attribute a, pg_am am, pg_attribute ai, pg_index i LEFT JOIN pg_proc ip ON (i.indpred = ip.oid)  WHERE ct.oid=i.indrelid AND ci.oid=i.indexrelid AND a.attrelid=ci.oid AND ci.relam=am.oid  AND ai.attnum = i.indkey[0] AND ai.attrelid = ct.oid  AND ct.relname = 'sql_sizing_profiles' ORDER BY NON_UNIQUE, TYPE, INDEX_NAME, ORDINAL_POSITION;

What is strange is that column pg_index.indproc was available in PostgresQL 7.3 (https://www.postgresql.org/docs/7.3/static/catalog-pg-index.html).
Can it be that liquibase fails to recognise PostgresQL 10 and falls back to some default logic? Although Pg 7.2 should be way too for any kind of support by liquibase.

Thanks,
Gin


↧

Set search_path and not use public

November 27, 2017, 1:05 pm
$
0
0
I am running liquibase on Redshift and it looks like I need to have a specific command in my script to 

'set search_path to my_non_public_db'

otherwise, it basically creates everything in public. Hardcoding this statement in the liquibase gets around the problem , however, I want to try and not do it.

Tried the switches

 --defaultSchemaName=my_db  --defaultCatalogName=my_db


but did not help.


Any suggestions?


↧

mvn plugin not working

December 7, 2017, 9:41 am
$
0
0
Hi guys
I´m trying to do a rollback for the very first time and i´m doing  via maven plugin with this command:
  1. liquibase:rollback -Dliquibase.rollbackTag=1.17
But maven responds me with this error:

  1.  BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.516 s
[INFO] Finished at: 2017-12-07T13:37:13-02:00
[INFO] Final Memory: 11M/155M
[INFO] ------------------------------------------------------------------------
[ERROR] No plugin found for prefix 'liquibase' in the current project and in the plugin groups
  2.  [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories 
  3.  [local (C:\Users\romulo\.m2\repository), central (https://repo.maven.apache.org/maven2)]
However i already inserted  the plugin:
here´s my pom.xml:

  1. <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
       <modelVersion>4.0.0</modelVersion>

       <groupId>PlayManager_LiquiBase</groupId>
       <artifactId>PlayManager_LiquiBase</artifactId>
       <version>1.7.0</version>
       <packaging>jar</packaging>

       <name>PlayManager_LiquiBase</name>
       <properties>
          <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
       </properties>

       <dependencies>
          <dependency>
             <groupId>org.liquibase</groupId>
             <artifactId>liquibase-core</artifactId>
             <version>3.4.2</version>
          </dependency>
            <!-- https://mvnrepository.com/artifact/org.liquibase/liquibase-maven-plugin -->
            <dependency>
                <groupId>org.liquibase</groupId>
                <artifactId>liquibase-maven-plugin</artifactId>
                <version>3.5.3</version>
            </dependency>

            <dependency>
             <groupId>mysql</groupId>
             <artifactId>mysql-connector-java</artifactId>
             <version>5.1.38</version>
          </dependency>
          <dependency>
             <groupId>org.apache.maven.plugins</groupId>
             <artifactId>maven-checkstyle-plugin</artifactId>
             <version>2.17</version>
             <type>maven-plugin</type>
          </dependency>
       </dependencies>

       <build>
          <plugins>
             <plugin>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.1</version>
                <configuration>
                   <source>1.8</source>
                   <target>1.8</target>
                </configuration>
             </plugin>


             <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-assembly-plugin</artifactId>
                <executions>
                   <execution>
                      <phase>package</phase>
                      <goals>
                         <goal>single</goal>
                      </goals>
                   </execution>
                </executions>
                <configuration>
                   <archive>
                      <manifest>
                         <mainClass>liquibase.integration.commandline.Main</mainClass>
                      </manifest>
                   </archive>
                   <descriptorRefs>
                      <descriptorRef>jar-with-dependencies</descriptorRef>
                   </descriptorRefs>
                   <finalName>PlayManager_LiquiBase</finalName>
                   <appendAssemblyId>false</appendAssemblyId>
                </configuration>
             </plugin>
          </plugins>

       </build>

    </project>
What i´m doing wrong?
↧
↧

Re : mvn plugin not working

December 7, 2017, 10:17 am
$
0
0
Your problem is that you declared a dependency to the liquibase-maven-plugin and not the use of it.

You need to include the plugin in the <plugins> section and a <dependency> to the jdbc driver of your database.

This is not related to the rollback. Any other goal can not work this way too.
↧

what is the default value for a column of type boolean which is nullable?

December 8, 2017, 10:39 am
$
0
0
what is the default value for a column of type boolean which is nullable?

I assume it is null but just would like to check
↧

Can we Hadoop Hive Database?

December 26, 2017, 5:20 am
$
0
0
 Hi,
I'm new to Hadoop Hive, now I'm interfacing Hive PHP utilizing Apache thrift, its working great. Do I need to know where is the Hive Database record store on the server ? (Database document way). Would anybody be able to please help me, I need to exchange my tables to another server.

Thank u for helpful suggestions?
↧
Search

diffChangeLog with Firebird databases

December 28, 2017, 6:52 am
$
0
0
I was making some tests with diffChangeLog command, and it seems to be strange.
If i compare the same database in Firebird, it brings me a lot of changes, like this:

  2.     <changeSet author="Victor (generated)" id="1514462714292-1">
  3.         <dropUniqueConstraint constraintName="BACKUPARMAZENAMENTO_UNQ01" tableName="TB_BACKUPARMAZENAMENTO"/>
  4.         <addUniqueConstraint columnNames="" constraintName="BACKUPARMAZENAMENTO_UNQ01" tableName="TB_BACKUPARMAZENAMENTO"/>
  5.     </changeSet>
  6.     <changeSet author="Victor (generated)" id="1514462714292-2">
  7.         <dropUniqueConstraint constraintName="BACKUPEXECHORA_UNQ01" tableName="TB_BACKUPEXECHORA"/>
  8.         <addUniqueConstraint columnNames="" constraintName="BACKUPEXECHORA_UNQ01" tableName="TB_BACKUPEXECHORA"/>
  9.     </changeSet>
  10.     <changeSet author="Victor (generated)" id="1514462714292-3">
  11.         <dropUniqueConstraint constraintName="CONFIGCIAPCFOP_UNQ" tableName="TB_CONFIGCIAPCFOP"/>
  12.         <addUniqueConstraint columnNames="" constraintName="CONFIGCIAPCFOP_UNQ" tableName="TB_CONFIGCIAPCFOP"/>
  13.     </changeSet>
Note that columnNames, are empty.

Why it is happen and why diff brings differences between the same database ?

PS.: It don't happen with postgresql database
↧
↧

Clob with Base64

December 30, 2017, 6:00 am
$
0
0
I have currently a clob column in oracle db where i am storing the value in base64 format, how this can be done using liquibase

I tried as given below

 <insert tableName="IMAGES"> 
<column name="IMAGE" valueClobFile="myimage.png" type="CLOB" />

even though liquibase inserted the value, it is not storing as base64.

FYI : I don't want to use BLOB, I am using CLOB to store the data in base64

↧

Hadoop HDFS: DateNode directory on system partition?

January 2, 2018, 3:53 am
$
0
0
 Hi,

We come up short on space on our Hadoop Cluster that is set up thusly: 

1x 1TB HDD/<-Ubuntu System Partition 

3x 1.5TB HDD/data1/data2/data3 <-HDFS Data Volumes 

The framework parcel is nearly not utilized (97% free) and won't be utilized for undertakings disconnected to Hadoop. 

Is it safe to include the framework parcel as HDFS information dir to the DataNode Configuration? 

I'm anxious about the possibility that that Hadoop tops off the segment and make the framework unusable. 

The ideal way would presumably to set up separate lvm volumes or re-parcel the plate. In any case, I would abstain from going along these lines. 

Does Hadoop regard Unix shares? E.g. in the event that I include an index from the framework segment and confine the Hadoop client through share to just utilize e.g. 0.5TB would that assistance?
↧

Need suggestion for best approach to deploy Liquibase on legacy product using RPM

January 8, 2018, 8:02 am
$
0
0
I have an application that is currently deployed via RPM. I'm working on including database migration as part of this, and am trying to determine best approach that accomplishes the ability to deploy the same RPM in either a new system or existing one, and have all the appropriate changesets (including legacy schema generated via generateChangeLog) deployed as part of the RPM postinstall.

We have the generated changelog of the existing schema, and I understand how future work will proceed as new schema changes are introduced via changesets, but so far am having trouble closing my gap in understanding about how to use conditionals/contexts/changeLogSync in order to accomplish what I am trying to do.

I think ideally the RPM would do something like this pseudocode:

1) check if legacy generated changelog file needs to be applied
2) run normal update

I just don't know if I would accomplish this by multiple command line invocations, or if there is a smarter way to organize my main changelog file. I don't particularly like the idea of contexts, because then I need something outside of the RPM to tell it how to be executed as a certain context, when it would be more ideal to be able to drop anywhere.

Other than this, I gotta say this is a kickass tool and I can't wait to have it deployed as part of our solution here.

Would appreciate any advice! Thanks!
↧

How to generate liquibase change logs along with basic preconditions ?

January 22, 2018, 3:08 am
$
0
0
Hi,

I used generateChangeLog command on an existing database. It helped me auto generating 'create' changesets for all tables, sequences. 

I am interested to know if there is a way to doing same and get preconditions included using generateChangeLog. Say to include basic precondition like if table or sequence already exists.

I went through liquibase documentation but couldn't find any help on this. Googled, but couldn't find much relevant, useful help.

Can anyone let me know if this is possible ?
I can help myself if pointed out to any useful knowledge source too.

Any help is appreciated.

More details:
database: postgres 9.5
liquibase-maven-plugin: 3.4.1
↧
↧

Re : How to generate liquibase change logs along with basic preconditions ?

January 22, 2018, 3:48 am
↧

Re : How to generate liquibase change logs along with basic preconditions ?

January 22, 2018, 11:21 am
$
0
0
In general, you don't need to have preconditions for things like 'table exists' before the change that creates a a table because liquibase will see that the change to create the table has already been applied, and won't try to re-apply it. 

If you have an existing database that you are starting to bring under Liquibase management, see the page http://www.liquibase.org/documentation/existing_project.html for some ideas on how to get started. 

Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/
↧
Search

NullPointerException when using `addColumn`

January 27, 2018, 2:41 pm
$
0
0
Hey all,

I'm getting an error with a simple liquibase setup. I've provided details in this stackoverflow question: liquibase-simple-changelog-nullpointerexception

I've also created a simple repo with the bug here: liquibase-add-column-bug

I simply want to create a new changeset that adds a column to an existing table but liquibase fails with a NullPointerException. What am I doing wrong? Thanks.

Liquibase: 3.5.3
Maven: 3.3.9
↧

generateChangeLog fails to include columns in createTable commands

January 30, 2018, 11:04 am
$
0
0
Hello, I'm new to Liquibase and am looking to see how it can be used on an already existing project.  I found the documentation on how to generate a changelog against our existing MySql DB.  But all of my attempts to do so have created changelogs which fail validation as part of a later update/changeLogSync command due to the fact that no column definitions are included in the create table commands.

In case it illuminates a mistake I'm making, there's the command I ran:

>java -jar c:\shortenedPath\liquibase-core-3.5.3.jar --driver=com.mysql.jdbc.Driver --classpath=c:\shortenedPath\mysql-connector-java-5.1.42.jar --changeLogFile=changelog.mysql.xml --url=jdbc:mysql://localhost/mySchema --username=root --password=password --logLevel=DEBUG --defaultSchemaName=mySchema generateChangeLog

and here's a snippet of the generated changelog:

<?xml version="1.1" encoding="UTF-8" standalone="no"?>
    <changeSet author="elumpkin (generated)" id="1517330636868-1">
        <createTable tableName="accesscontrolgroup"/>
    </changeSet>
    <changeSet author="elumpkin (generated)" id="1517330636868-2">
        <createTable tableName="accessgroup"/>
    </changeSet>
    <changeSet author="elumpkin (generated)" id="1517330636868-3">
        <createTable tableName="accountuser"/>
    </changeSet>
    ....
 </databaseChangeLog>

Lastly I'm running this against a local mysql DB which claims to be version 5.6.26-log running on Win7.  Hopefully I'm just doing something wrong/dumb and you can point me in the better direction.  Thanks!

-Erik
↧
↧

Re : generateChangeLog fails to include columns in createTable commands

January 31, 2018, 10:54 am
$
0
0
It sounds like you are doing reasonable steps and getting unexpected results. I see you have logLevel debug already set, can you share the logs?

Steve Donie
Principal Software Engineer
Datical, Inc. http://www.datical.com/
↧

Re : generateChangeLog fails to include columns in createTable commands

January 31, 2018, 5:19 pm
$
0
0
Sure.  Sorry it's a bit ugly (thanks terrible windows command line).

C:\Users\elumpkin\Desktop>java -jar c:\Users\elumpkin\.gradle\caches\modules-2\f
iles-2.1\org.liquibase\liquibase-core\3.5.3\f346404c3876c5bd0e07a7e10b7565bdcd35
dbab\liquibase-core-3.5.3.jar --driver=com.mysql.jdbc.Driver --classpath=c:\User
s\elumpkin\.gradle\caches\modules-2\files-2.1\mysql\mysql-connector-java\5.1.42\
80a448a3ec2178b649bb2e3cb3610fab06e11669\mysql-connector-java-5.1.42.jar --chang
eLogFile=changelog.mysql.xml --url=jdbc:mysql://localhost/cais --username=root -
-password=password --logLevel=DEBUG --defaultSchemaName=cais generateChangeLog
DEBUG 1/31/18 5:17 PM: liquibase: Connected to root@localhost@jdbc:mysql://local
host/cais
DEBUG 1/31/18 5:17 PM: liquibase: Setting auto commit to false from true
DEBUG 1/31/18 5:17 PM: liquibase: Executing EXECUTE database command: USE cais
DEBUG 1/31/18 5:17 PM: liquibase: Computed checksum for 1517440651454 as 5842fe5
70773e5316474acef11f7cfca
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='campaig
nreferral' and const.constraint_name='emailaddress_unique'order by ordinal_posit
ion
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='campaig
nreferral' and const.constraint_name='campaigntoken_unique'order by ordinal_posi
tion
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='fundmap
ping' and const.constraint_name='unique'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='adminad
visorteam' and const.constraint_name='uniq'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='redempt
ion_document' and const.constraint_name='fundid_unique'order by ordinal_position

DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='positio
n_by_nav' and const.constraint_name='id_unique'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='positio
n' and const.constraint_name='positionid_unique'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='sharecl
assdocument' and const.constraint_name='shareclassdocumentclient'order by ordina
l_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='acl_sid
' and const.constraint_name='unique_uk_1'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='rebate_
by_nav' and const.constraint_name='id_unique'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='adminin
vestmententity' and const.constraint_name='uniq'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='ofacven
dor' and const.constraint_name='vendorid_unique'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='product
documents' and const.constraint_name='uniq'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='investm
ententitydocument' and const.constraint_name='uniq'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='acl_cla
ss' and const.constraint_name='unique_uk_2'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='cmequit
yoffering' and const.constraint_name='internalcusip_unique'order by ordinal_posi
tion
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='cmprefe
rredofferings' and const.constraint_name='internalcusip_unique'order by ordinal_
position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='documen
t' and const.constraint_name='documentid_unique'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='documen
t' and const.constraint_name='hasheddocid_unique'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='fundser
ies' and const.constraint_name='fundseriesid_unique'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='fundser
ies' and const.constraint_name='fundshareclass-uniq'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='acl_obj
ect_identity' and const.constraint_name='unique_uk_3'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select const
.CONSTRAINT_NAME, COLUMN_NAME from information_schema.table_constraints const jo
in information_schema.key_column_usage col on const.constraint_schema=col.constr
aint_schema and const.table_name=col.table_name and const.constraint_name=col.co
nstraint_name where const.constraint_schema='cais' and const.table_name='acl_ent
ry' and const.constraint_name='unique_uk_4'order by ordinal_position
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select view_
definition from information_schema.views where table_name='vw_weeklyestimates' a
nd table_schema='cais'
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select view_
definition from information_schema.views where table_name='vw_populatechartdatab
ytotalfunds' and table_schema='cais'
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select view_
definition from information_schema.views where table_name='vw_producttype' and t
able_schema='cais'
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select view_
definition from information_schema.views where table_name='hierarchyrelationship
' and table_schema='cais'
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select view_
definition from information_schema.views where table_name='vw_monthlyactuals' an
d table_schema='cais'
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select view_
definition from information_schema.views where table_name='vw_uncomplete_task' a
nd table_schema='cais'
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select view_
definition from information_schema.views where table_name='vw_available_offshore
_funds' and table_schema='cais'
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select view_
definition from information_schema.views where table_name='vw_factsheetdata' and
 table_schema='cais'
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select view_
definition from information_schema.views where table_name='vw_monthlyestimates'
and table_schema='cais'
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select view_
definition from information_schema.views where table_name='vw_positiongraphdata'
 and table_schema='cais'
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select view_
definition from information_schema.views where table_name='vw_available_onshore_
funds' and table_schema='cais'
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select view_
definition from information_schema.views where table_name='vw_facetednav' and ta
ble_schema='cais'
DEBUG 1/31/18 5:17 PM: liquibase: Executing QUERY database command: select view_
definition from information_schema.views where table_name='vw_gettaskstatus' and
 table_schema='cais'
INFO 1/31/18 5:17 PM: liquibase: Can not use class liquibase.serializer.core.yam
l.YamlChangeLogSerializer as a Liquibase service because org.yaml.snakeyaml.repr
esenter.Representer is not in the classpath
INFO 1/31/18 5:17 PM: liquibase: Can not use class liquibase.serializer.core.jso
n.JsonChangeLogSerializer as a Liquibase service because org.yaml.snakeyaml.repr
esenter.Representer is not in the classpath
INFO 1/31/18 5:17 PM: liquibase: changelog.mysql.xml does not exist, creating
DEBUG 1/31/18 5:17 PM: liquibase: MissingObjectChangeGenerator type order:     l
iquibase.structure.core.Catalog    liquibase.structure.core.Schema    liquibase.
structure.core.Sequence    liquibase.structure.core.StoredProcedure    liquibase
.structure.core.Table    liquibase.structure.core.Column    liquibase.structure.
core.PrimaryKey    liquibase.structure.core.UniqueConstraint    liquibase.struct
ure.core.Index    liquibase.structure.core.ForeignKey    liquibase.structure.cor
e.View
DEBUG 1/31/18 5:17 PM: liquibase: UnexpectedObjectChangeGenerator type order:
  liquibase.structure.core.Catalog    liquibase.structure.core.ForeignKey    liq
uibase.structure.core.Schema    liquibase.structure.core.StoredProcedure    liqu
ibase.structure.core.UniqueConstraint    liquibase.structure.core.View    liquib
ase.structure.core.Table    liquibase.structure.core.PrimaryKey    liquibase.str
ucture.core.Column    liquibase.structure.core.Index    liquibase.structure.core
.Sequence
DEBUG 1/31/18 5:17 PM: liquibase: ChangedObjectChangeGenerator type order:     l
iquibase.structure.core.Catalog    liquibase.structure.core.ForeignKey    liquib
ase.structure.core.Schema    liquibase.structure.core.Sequence    liquibase.stru
cture.core.StoredProcedure    liquibase.structure.core.Table    liquibase.struct
ure.core.Column    liquibase.structure.core.PrimaryKey    liquibase.structure.co
re.UniqueConstraint    liquibase.structure.core.Index    liquibase.structure.cor
e.View
Liquibase 'generateChangeLog' Successful
↧

Release Updates

February 1, 2018, 4:39 pm
$
0
0

Liquibase Community,


I want to provide a quick update on the promise I made near the end of last year about maintaining a healthier update cadence to the Liquibase project. The Datical leadership team remains committed to this goal as well, and after getting some time in the new year to look into some of the open pull requests, I’m excited to share what’s next.


Right now, my plan is to have a 3.5.4 release out in the next month or so which will include Java 9 Support along with a number of bug fixes. I know that Java 9 has long been anticipated by the community, and is a meaningful step forward for

the project. The release notes will detail the specifics in greater detail.


To follow on, sometime in February, I’m planning a 3.6 release. There is still some work on my end to figure out exactly what will be a part of 3.6 release, but after going through all the pull requests against Liquibase, it’s clear that there’s enough substance to warrant a 3.6 release as soon as possible as well.


I’m looking forward to a investing more of my time this year into Liquibase and am proud of the strong and engaged community that has formed around this project. If you have interest in stepping up to help commit changes and more actively assist me in maintaining the project, please let me know. I don’t want to be a bottleneck to progress on this project, and I welcome your help.


Thanks, and Happy 2018!

Nathan

↧
Viewing all 1169 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>