Maven 2.x SQL Plugin

Tables with foreign keys can not be imported into MySQL

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Not A Bug
  • Affects Version/s: 1.4
  • Fix Version/s: None
  • Labels:
    None
  • Environment:
  • Testcase included:
    yes
  • Number of attachments :
    3

Description

I am trying to create a database with tables, having foreign keys attached to them. Unfortunately I am getting strange error:

Can't create table 'testdb.configuration' (errno: 150)

from maven. The same SQL file, if imported into MySQL with command-line client, gets imported without any error.

If you remove foreign key declaration - tables will be created without any error.

I attached the package with sample Maven project.

Thank you in advance!

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Johan Romme added a comment -

I've been trying to reproduce this error, did not succeed. Unpacked the zip,
2 minor changes in the pom.xml (initial database and root password), and
'mvn test' ends with 'BUILD SUCCESSFULL', nothing strange in the output.

Maybe you can supply a more consequently failing example of the problem
mentioned in the issue.

My platform: Ubuntu-8.04, mysql-5.0.15-, sun-java-1.6.0.20, mvn-2.2.1/2.0.10.

Show
Johan Romme added a comment - I've been trying to reproduce this error, did not succeed. Unpacked the zip, 2 minor changes in the pom.xml (initial database and root password), and 'mvn test' ends with 'BUILD SUCCESSFULL', nothing strange in the output. Maybe you can supply a more consequently failing example of the problem mentioned in the issue. My platform: Ubuntu-8.04, mysql-5.0.15-, sun-java-1.6.0.20, mvn-2.2.1/2.0.10.
Hide
Permalink
Eugene Dzhurinsky added a comment -

Can you please try it out with MySQL 5.1 and 5.5 ?

Show
Eugene Dzhurinsky added a comment - Can you please try it out with MySQL 5.1 and 5.5 ?
Hide
Permalink
Johan Romme added a comment -

maven output for the sqltest using mysql-5.1.48

Show
Johan Romme added a comment - maven output for the sqltest using mysql-5.1.48
Hide
Permalink
Johan Romme added a comment -

maven output for the sqltest using mysql-5.5.3-m3

Show
Johan Romme added a comment - maven output for the sqltest using mysql-5.5.3-m3
Hide
Permalink
Johan Romme added a comment -

Found some spare time to respond to your request to run the same test using
mysql-5.1 and mysql-5.5. I added a 'select version();' to the sql in the
pom.xml, so one can see which version of mysql the server is running. The
result of both test runs I attached to the issue.
As you can see the test runs fine with mysql-5.1(.48), but the test fails
with 5.5.3-m3 in the manner you describe in the issue.
Question remains whether the bug has to do with sql-maven-plugin or with the
new (development) mysql server version, I'd vote for the last..

Show
Johan Romme added a comment - Found some spare time to respond to your request to run the same test using mysql-5.1 and mysql-5.5. I added a 'select version();' to the sql in the pom.xml, so one can see which version of mysql the server is running. The result of both test runs I attached to the issue. As you can see the test runs fine with mysql-5.1(.48), but the test fails with 5.5.3-m3 in the manner you describe in the issue. Question remains whether the bug has to do with sql-maven-plugin or with the new (development) mysql server version, I'd vote for the last..
Hide
Permalink
Robert Scholte added a comment -

Thanks Johan for figuring this out. I've done some extra googling for errnr: 150, found enough hits. It seems like both columns have to be EXACLTY the same. And that looks like the problem, since int(11) is not the same as INTEGER.
On way or another, it's not a sql-m-p bug, there's really nothing we can do about it.

Show
Robert Scholte added a comment - Thanks Johan for figuring this out. I've done some extra googling for errnr: 150 , found enough hits. It seems like both columns have to be EXACLTY the same. And that looks like the problem, since int(11) is not the same as INTEGER. On way or another, it's not a sql-m-p bug, there's really nothing we can do about it.

People

  • Assignee:
    Robert Scholte
    Reporter:
    Eugene Dzhurinsky
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: