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

sea-orm-cli does not process tables with system versioning enabled [mariadb] #848

Closed
mohs8421 opened this issue Jul 7, 2022 · 3 comments · Fixed by SeaQL/sea-schema#76
Closed
Assignees

Comments

@mohs8421
Copy link
Contributor

mohs8421 commented Jul 7, 2022

I wanted to import a table that I generated on mariadb with system versioning feature (https://mariadb.com/kb/en/system-versioned-tables/), and was surprised that the entity file was not generated at all (there also was no error message about that).
After I dropped the system versioning for that table, it was recognized properly.

@tyt2y3 tyt2y3 changed the title sea-orm-cli does not process tables with system versioning enabled sea-orm-cli does not process tables with system versioning enabled [mariadb] Jul 10, 2022
@billy1624 billy1624 moved this to Triage in SeaQL Dev Tracker Jul 12, 2022
@billy1624
Copy link
Member

Hey @mohs8421, sorry for the delay. Could you provide a sample DDL for the table with system versioning? So that I can test it on my machine. Thanks!!

@mohs8421
Copy link
Contributor Author

CREATE TABLE `example` (
  `example_id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `data` varchar(255) NOT NULL,
  PRIMARY KEY (`example_id`)
) WITH SYSTEM VERSIONING

@billy1624
Copy link
Member

Thanks! @mohs8421 I've just created PRs fixing it. You can try it out :)

Running sea-orm-cli from source code

@billy1624 billy1624 moved this from Triage to Done in SeaQL Dev Tracker Jul 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
2 participants