-
Notifications
You must be signed in to change notification settings - Fork 77
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
ERROR - Failed to extract the SQL Database Schema: Cannot handle repeated column sid in table addressable #964
Comments
hi,
it looks like from a SQL query on the schema, the column name Which version of MySQL are you using? |
hmmm... I am trying to understand how something like this is even possible... by any chance, is the combination of name schema/table for |
@jgaleotti do you have any insight on how this could be happening? |
Hi @arcuri82 @jgaleotti, desc tmf632_party_management.addressable; desc tmf720_digital_identity_management.addressable; |
@aruvic thanks for providing these extra details. it seems related to issue #806 it seems like we do not properly handle the case of multiple schemas in the database. |
Hi @arcuri82 @jgaleotti , I just want to confirm that you are searching in all schemas instead in only one.
the code is ignoring the provided schema name in via --spring.datasource.url=
|
Hi @aruvic , indeed, there are quite a few issues related with the current handling of multi-schema databases. I looked into it, and it would take quite a bit of changes throughout the whole code-base of EvoMaster to fix it. But currently we are in the middle of other important features/fixes to complete first. For the time being, until this is solved, I would suggest to simply return |
Below error is produced by JDK17 Spring Boot driver using EvoMaster 3.0.0
DB table:
![image](https://private-user-images.githubusercontent.com/40695592/325559828-06fed27e-12bd-49b3-9ee4-5b4e3f1af525.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQwMzYyODQsIm5iZiI6MTcyNDAzNTk4NCwicGF0aCI6Ii80MDY5NTU5Mi8zMjU1NTk4MjgtMDZmZWQyN2UtMTJiZC00OWIzLTllZTQtNWI0ZTNmMWFmNTI1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE5VDAyNTMwNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTMyMWY1NTE2MDhmNGU5YjdmZGM5YWIzMzE0YTliYTgxYjBmMzIxYTg4ZjViZTAwNDQ3N2FjNTg5MWJmZGE1YWYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.csP6VAR6YM-62-Lzh1Yc_11MvFQOYEbtEx5qW2WWw2c)
driver:
The text was updated successfully, but these errors were encountered: