You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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.
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
The text was updated successfully, but these errors were encountered: