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

cannot open siard with arrays #305

Open
Laurira opened this issue Nov 3, 2021 · 2 comments · May be fixed by #459
Open

cannot open siard with arrays #305

Laurira opened this issue Nov 3, 2021 · 2 comments · May be fixed by #459

Comments

@Laurira
Copy link

Laurira commented Nov 3, 2021

Postgresql database had ARRAY-s in it but the siard was created with no errors.

But it cannot be opened with Desktop or Enterprise, it gives error
image

Siard->metadata.xml
image

@Laurira
Copy link
Author

Laurira commented Nov 3, 2021

This is from DBPTK-Desktop log:
2021-11-03 12:11:59,486 [http-nio-auto-1-exec-4] INFO c.d.m.siard.update.SIARDEditModule - Importing SIARD version 2.1
2021-11-03 12:12:04,364 [http-nio-auto-1-exec-1] ERROR c.d.c.c.c.utils.AsyncCallbackUtils - [127.0.0.1] AsyncCallback error - RESTException: Remote exception caused by GenericException: Arrays are not yet supported. caused by ViewerException: Arrays are not yet supported.

@Laurira
Copy link
Author

Laurira commented Nov 16, 2021

Our suggestion is that in this case the application should not tell the user "it can not be done". Instead it should just convert those array fields to varchar and continue with warning that "as arrays are not supported then these fields were converted into varchar".

At the moment we edited our siard file and made that change by hand. After this modification the siard file was exported nicely into the dbptk enterprise and is browsable as well.

@AntonioG70 AntonioG70 linked a pull request Dec 23, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant