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

There should be a way to create an index for an already existing table #31

Open
orium opened this issue Apr 19, 2016 · 4 comments
Open

Comments

@orium
Copy link

orium commented Apr 19, 2016

No description provided.

@rpvilao
Copy link
Collaborator

rpvilao commented Apr 19, 2016

Adding on demand or after in general? Because after in general is possible - you just add the new one and if it doesn't exist it will be created.

@orium
Copy link
Author

orium commented Apr 19, 2016

Not sure if I get what on-demand/after-in-general means. In my case I have a table that is created elsewhere (and I don't have access to the entity definition), where I just know that a few columns exist and I want and index on those columns.

@defer
Copy link
Collaborator

defer commented Apr 19, 2016

I can imagine of a few use cases for this like schema migrations.

But, in general, creating and updating DML in different places and with only partial knowledge of of the entity feels wrong.

@rpvilao
Copy link
Collaborator

rpvilao commented Apr 19, 2016

yep it's true. but that would be the approach being wrong and not the feature it self as you said. I don't see any harm to have it. whether it's properly used or not it's a different matter.

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