Nathan Voxland

Moorhead, MN

nathan.voxland.net

Age: 39

Primarily Java developer. Started and run the open source Liquibase database change management tool.

Mar
3
awarded Good Answer
Feb
18
awarded Notable Question
Jan
27
awarded Nice Answer
Dec
12
awarded Yearling
Dec
12
awarded Yearling
Nov
20
answered Liquibase - Mass Applying ChangeSets where packages change over time
Nov
18
answered Should Liquibase cope with concurrent initialisation?
Nov
4
comment DDL command not created by liquibase when trying to run it from Java code
The ResourceAccessor is what is used to look up the changelog, including the path. If you are using ClassLoaderResourceAccessor, the path should be more like just "changelog.xml" since src/main/resources will end up as a classpath root. If you want to (or need to) use the full /src/main/resources/changelog.xml, you'll probably need to use FileSystemResourceAccessor instead
Nov
4
answered DDL command not created by liquibase when trying to run it from Java code
Oct
29
awarded Custodian
Oct
29
reviewed Approve suggested edit on liquibase <insert> : Insert current date
Oct
23
comment How to ignore the splitting character in strings with Liquibase SQL syntax
Thanks, I'll take a look
Oct
22
answered Liquibase intellij integration?
Oct
22
comment How to ignore the splitting character in strings with Liquibase SQL syntax
What version of Liquibase are you using? Newer versions have improved the SQL parsing some
Oct
22
comment Liquibase uses full paths with includeAll tag
Which version of Liquibase are you using currently?
Oct
22
comment Liquibase different behavior when using CLI and Maven
Command line liquibase has a -classpath attribute. Make sure that is set to include the same classpath root(s) that contain changelog files as Maven is using.
Oct
22
comment Liquibase different behavior when using CLI and Maven
Instead of specifying the logicalFilePath you can ensure that the classpath you are using in the command line matches the maven classpath. But logicalFilepath ensures they are they seen as the same.
Aug
31
answered liquibase changeset onupdating to 3.2.3
Jul
30
comment missing column 'CONTEXTS' after Liquibase migration to version 3.4.0 from 2.0.4
Liquibase 3.4.1 fixes the issue so you can run status before running update now.
Jul
30
comment missing column 'CONTEXTS' after Liquibase migration to version 3.4.0 from 2.0.4
Status and updateSQL do not change the database, which is why init() is not called. Liquibase 3.4.1 resolves the issue by using "SELECT *" instead of explicitly listing the columns which may not actually be there.
1 2 3 4 5