Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Liquibase.dropAll error: Failed to determine if the table has a geometry column... #1

Closed
TimWalker opened this issue Jun 12, 2014 · 3 comments
Milestone

Comments

@TimWalker
Copy link

Hi,

I am attempting to use the liquibase-spatial plugin with my H2 unit tests. The first thing my unit tests always do is to drop all tables in the database, using the dropAll Liquibase method which works just fine until I try to get things working to support spatial data. When I enable this I get the error: Failed to determine is the table has a geometry column.

My pom is copied below and I can provide any additional information.

I'd like to get this working so we can continue to use H2 in our test environments.

Thank you very, very much,

Tim


4.0.0

com.digitalglobe.databaseMigration
databaseMigration
1.0-SNAPSHOT
jar

databaseMigration
http://maven.apache.org

UTF-8 com.github.lonnyj liquibase-spatial 1.0.0 com.h2database h2 1.4.178 test org.liquibase liquibase-core 3.1.1 test junit junit 4.10 test
@TimWalker TimWalker changed the title Liquibase.dropAll error: Failed to determine is the table has a geometry column... Liquibase.dropAll error: Failed to determine if the table has a geometry column... Jun 12, 2014
@lonnyj
Copy link
Owner

lonnyj commented Jun 16, 2014

Do you have an exception that you can include? I'm guessing that the database isn't spatialized so a query is failing on geometry_columns. I've committed a change. Please give that a try if you can and see if that fixes the problem.

@TimWalker
Copy link
Author

Hi Lonny!

Thank you very much for the reply. When I get a chance I will try that
again and let you know. Might be a few days...

Thank you again, and thanks for taking a stab at the potential culprit!

Sincerely,

Tim

On Sun, Jun 15, 2014 at 9:25 PM, lonnyj notifications@github.com wrote:

Do you have an exception that you can include? I'm guessing that the
database isn't spatialized so a query is failing on geometry_columns.
I've committed a change. Please give that a try if you can and see if that
fixes the problem.


Reply to this email directly or view it on GitHub
#1 (comment)
.

@lonnyj
Copy link
Owner

lonnyj commented Nov 1, 2014

This issue is fixed in 1.0.1 and 1.1.0.

@lonnyj lonnyj closed this as completed Nov 1, 2014
@lonnyj lonnyj modified the milestones: 1.1.0, 1.0.1 Nov 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants