search

budde377 / Part

Framework for developing websites written in PHP/Dart.
MIT License
2 stars 0 forks source link

Figure a way to roll out changes to database #69

Closed budde377 closed 9 years ago

budde377 commented 9 years ago

On update, check if there has been added new files in db. If so run it and mark it run.

Imported from Bitbucket Originally reported by: Christian Budde Christensen (2014-07-06T14:28:45.693)

budde377 commented 9 years ago

Supplement with db file for each table. If table doesn't exist run sql. This would also justify the use of the DB class...

Original comment by: Christian Budde Christensen (2014-08-27 17:30:47+00:00)

budde377 commented 9 years ago

Mark it could be done in MySQL

Original comment by: Christian Budde Christensen (2014-10-07 19:22:47+00:00)

budde377 commented 9 years ago

Add folders to look for tables in site-config. Support for multiple folders and consider hardwired default folder

Original comment by: Christian Budde Christensen (2014-10-07 19:26:35+00:00)

budde377 commented 9 years ago

Marking done with saving hash

Original comment by: Christian Budde Christensen (2014-10-07 19:28:26+00:00)

budde377 commented 9 years ago

hash bad idea.

Original comment by: Christian Budde Christensen (2014-10-07 19:29:17+00:00)

budde377 commented 9 years ago

Lets postpone this. The current solution doesn't fully meet our requirements and it isn't that important with the new update scheme.

Original comment by: Christian Budde Christensen (2014-10-10 23:20:10+00:00)

budde377 commented 9 years ago

Let's do the following:

  1. Keep a version table
  2. Register db folders in site-config.xml
  3. In the db folders create subfolders for each db namespace
  4. Name sql files in folder with namespace and version
  5. Upgrade version table after installing version.
  6. Add variable to sql files representing cms and mail db.