database-versioning

Starting with versioning mysql schemata without overkill. Good solutions?

狂风中的少年 提交于 2019-12-18 11:42:56
问题 I've arrived at the point where I realise that I must start versioning my database schemata and changes. I consequently read the existing posts on SO about that topic but I'm not sure how to proceed. I'm basically a one man company and not long ago I didn't even use version control for my code. I'm on a windows environment, using Aptana (IDE) and SVN (with Tortoise). I work on PHP/mysql projects. What's a efficient and sufficient (no overkill) way to version my database schemata? I do have a

Database versioning without history tables

左心房为你撑大大i 提交于 2019-12-17 22:59:59
问题 I was going through this post for record level versioning of tables. I noticed that the architecture deals with the usage of history tables. However, my scenario does not require rollback but retrieving point in time records. This is where I have tried with a design on using a single table for versioning. Note that this is a bare bone table data (no constraints, indices, etc.). I intend to index based on id since this involves group by clause on the column. For example, I have got a table

Doctrine migrations fallback

时光总嘲笑我的痴心妄想 提交于 2019-12-14 03:46:35
问题 We're using doctrine migrations and there often are problems when the migration contains multiple actions and one of them fails. For example, if there is a migration adding 5 foreign keys and the 5th of them fails while fields aren't of the same length, fixing the error with the fields and regenerating migrations does not fix the whole thing, while now there is an error connected with the fact 4 of the keys already exists and don't allow the migration to run successfully. Is there a stable

SQL Server Database schema versioning and update

无人久伴 提交于 2019-12-09 19:01:14
问题 For my application I have to support update scenarios and the database might be affected. I want to be able to update from an old version to the newest without installing intermediate versions. E.g. Suppose I have version A (the oldest), B (intermediate) and C (new version). I want to be able to update version A straight to version C. For the application files this is simple, I just replace the old with the new ones. However for the database I do not wish to generate a SQL Script to change

Upgrading database version automatically

帅比萌擦擦* 提交于 2019-12-07 16:04:36
Hi i am creating an app which stores the password of the user entering. and whenever he needs to change his password then the data has to be changed. The problem i am facing is while i am calling the DBHelper class (i created to do all my database works) its not deleting the table if it is available. It will be more helpful if someone tells me how to delete the entries in the table while calling the DBHelper class. I realized that the OnCreate and OnUpgrade functions are not executing except the first time while creating the database. also changing database version automatically also helps i

Is there a way to generate Liquibase data in the right order?

无人久伴 提交于 2019-12-06 03:40:19
问题 I'm using Liquibase for versioning an existing database, so I'm using liquibase \ --logLevel=debug \ --driver=com.mysql.jdbc.Driver \ --classpath=lib/mysql-connector-java-5.1.30.jar \ --url="jdbc:mysql://127.0.0.1:3306/schema" \ --username=user \ --password=pass \ --diffTypes="data" \ --changeLogFile="./data.xml" generateChangeLog for generating the changeset xml. This works, but the problem is when I'm trying to run those generated changesets. I get Cannot add or update a child row: a

Database Version / Change Control for Data not Schema?

℡╲_俬逩灬. 提交于 2019-12-05 21:54:39
问题 After reading a few articles here and around, I have realised that database version control in a development team is actually of high importance. Until now I have been using a simple dump whole database each time there is an update, if only 1 table was altered sometimes we can get away with just dumping the single table then reimporting. Not the best but it works quite well, for additive changes and we haven't had any hiccups yet. Now, I save a .mwb (Mysql Workbench diagram) file in the git

Rails 3.2 app - Should I use a versioning gem (paper_trail or vestal_versions) or handle it manually?

情到浓时终转凉″ 提交于 2019-12-05 09:18:56
My question: Should I roll my own model versioning or use one of the versioning gems that's already out there? If I should use a gem, which one seems best for this application? Info about my app My app is a simple Checklist app. There are Checklists and Jobs, and I track user responses with Responses and Submissions. The Response tells me what the use said ("Done", with a note "We need more mops.") and the Submission tells me when that particular Checklist was filled out (because there may be many submissions and sets of responses for a given checklist). I'll show my associations below, in

SQL Server Database schema versioning and update

做~自己de王妃 提交于 2019-12-04 14:33:41
For my application I have to support update scenarios and the database might be affected. I want to be able to update from an old version to the newest without installing intermediate versions. E.g. Suppose I have version A (the oldest), B (intermediate) and C (new version). I want to be able to update version A straight to version C. For the application files this is simple, I just replace the old with the new ones. However for the database I do not wish to generate a SQL Script to change the database schema from A straight to C, instead I want first apply a script to change the schema from A

How to implement Auditing/versioning of Table Modifications on PostgreSQL

佐手、 提交于 2019-12-04 11:41:31
问题 We're implementing a New system using Java/Spring/Hibernate on PostgreSQL. This system needs to make a copy of Every Record as soon as a modification/deletion is done on the record(s) in the Tables(s). Later, the Audit Table(s) will be queried by Reports to display the data to the users. I was planning to implement this auditing/versioning feature by having a trigger on the table(s) which would make a copy of the modified row(deleted row) "TO" a TABLE called ENTITY_VERSIONS which would have