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

UUID handling broken, different output between DAO & DSL #1535

Closed
jonasborn opened this issue Jun 17, 2022 · 3 comments
Closed

UUID handling broken, different output between DAO & DSL #1535

jonasborn opened this issue Jun 17, 2022 · 3 comments

Comments

@jonasborn
Copy link

jonasborn commented Jun 17, 2022

Looks like there is a failure in UUID handling between DAO and DSL, probably related to #1467

image
image

Ubuntu Ubuntu 20.04.4 LTS x64
10.4.21-MariaDB - Source distribution
Protokoll-Version: 10
openjdk version "11.0.12" 2021-07-20 LTS
Kotlin version 1.6.21-release-334 (JRE 11.0.12+7-LTS)

using

exposed-core 0.38.2
exposed-jdbc 0.38.2
exposed-dao 0.38.2

Currently not sure, which UUID is the right one, will add a comment soon.

@jonasborn
Copy link
Author

jonasborn commented Jun 17, 2022

image

Looks like c794e160-35ae-40b9-8c6b-8c1c7b71fd48 is the original I've added using DSL before.

@AlexeySoshin
Copy link
Contributor

AlexeySoshin commented Aug 14, 2022

Looks like your first select queries Device table, not User table as the second one.

That's because in your entity definition you point to the wrong table. Should be
UUIDEntityClass<User>(UserTable)

@bog-walk
Copy link
Member

bog-walk commented May 9, 2023

Confirming that the printed UUID are equivalent after the proposed adjustment above. Please reopen this issue if the problem requires more answers.

@bog-walk bog-walk closed this as completed May 9, 2023
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

3 participants