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

split out the model generation code #73

Conversation

championswimmer
Copy link
Contributor

We have some extra types like JSONB and ARRAY(NUMERIC) we can use for Postgres, let's take advantage of that.

@championswimmer
Copy link
Contributor Author

championswimmer commented Sep 27, 2017

@pmcnr-hx @paparomeo
So I've split out model generation into seprate modules. Using a common 'default' module for everything other than Postgres right now, as my optimisations are only for Postgres. For others, it's the same.

@aledalgrande
Copy link
Contributor

@championswimmer could this also take care of #53 as you are splitting out by dialect?

@championswimmer
Copy link
Contributor Author

@aledalgrande this fixes #53 by making [type] a virtual field

@championswimmer
Copy link
Contributor Author

also, @aledalgrande do you think I can target postgres >= 9.4 ??
Will allow using JSONB type

Are you using < v9.4 ?

Signed-off-by: Arnav Gupta <[email protected]>
@aledalgrande
Copy link
Contributor

@championswimmer using latest stable, so it's fine!

@championswimmer
Copy link
Contributor Author

Continues to #75

pmcnr-hx added a commit that referenced this pull request Sep 30, 2017
…ttributes

split out the model generation code (contd from #73)
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 this pull request may close these issues.

2 participants