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

Using piccolo on legacy data #88

Closed
cheesycod opened this issue Apr 24, 2021 · 4 comments · Fixed by #157
Closed

Using piccolo on legacy data #88

cheesycod opened this issue Apr 24, 2021 · 4 comments · Fixed by #157

Comments

@cheesycod
Copy link

Is there a way to have piccolo work on legacy database schemas (like managed = False in django)

@dantownsend
Copy link
Member

@cheesycod There should be no problems with this - just define the models in Piccolo, and it can connect to existing database tables.

If using Piccolo migrations, the first time you run them you might want to use the fake flag.

piccolo migrations forwards some_app --fake

@vctrd
Copy link

vctrd commented Aug 9, 2021

Hello,

following up on this question, would an inspection mechanism such as python manage.y inspectdb to create the models in Piccolo automaticaly make sense ?

Thank you

@dantownsend
Copy link
Member

Hi @vctrd, that's a good idea.

I've started putting together a simple prototype - will try and release this soon, as I can see it being a big time saver for people.

#157

@vctrd
Copy link

vctrd commented Aug 9, 2021

Thank you very much, I'll have a look.

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.

3 participants