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

Automatic DB scheme update #103

Open
Masadow opened this issue May 12, 2014 · 3 comments
Open

Automatic DB scheme update #103

Masadow opened this issue May 12, 2014 · 3 comments

Comments

@Masadow
Copy link
Member

Masadow commented May 12, 2014

When the scheme of the database has changed, especially when a module is updated, the framework should be able to detect the change and update its tables structure accordingly

@ValentinTrinque
Copy link
Member

Is it possible to do it without killing performance for the framework? Isn't more interesting to provide a tool which analyse the DB scheme and update it if needed?

For example, we could simply write our DB scheme during the compilation and after, call a tool which verify the integrity of the existing DB.

Why I'm proposing this solution is because it's possible to already have a huge table with a lot of data in it, and apply changes on it can be really time-eager. Consequently, doing it inside the framework can either slow it down or cause trouble to the user. Indeed, if a user send a form and the DB scheme has changed then she/he could not understand why it takes 1 minutes to process or why it timeouts.

@Masadow
Copy link
Member Author

Masadow commented May 13, 2014

We could have a command like haxelib run beluga updatedb

Anyway, updating the db scheme shouldn't be that long since if I remember correctly, it's what is done within struts in java

@ValentinTrinque
Copy link
Member

I agree for your first proposition.

BTW, Struts isn't know to yield performance. I really think it's better to provide tool AROUND the framework for administrative matters rather than including this kind of process inside the framework.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants