database-versioning

问题 After reading a lot of SO questions about Keeping page changes history or How to version control a record in a database (for example), I can't find a real elegant solution to do the work. Now, let's try to explain as clear as possible what we need , for this simple revision system, that allows registered users to post some articles, and other users to submit a revision of those articles, and then some moderators users to check those revisions. MySQL database The database contains an articles

问题 I am trying to add three new table to my existing sqlite db and I'm running into problems with the db version not updating after a successful upgrade. Below is the DatabaseHelper that runs: private static class DatabaseHelper extends SQLiteOpenHelper { public DatabaseHelper(Context context, String name, CursorFactory factory, int version) { super(context, name, factory, version); } @Override public void onCreate(SQLiteDatabase db) { Log.w(TAG, "Current db version is " + db.getVersion()); db

问题 Could someone explain the concept of Migrators (specifically fluentmigrator)? Here are the (possibly confused) facts Ive gleaned on the subject: Is it a way to initially create then maintain updates for a database by way of versioning. The first migration (or initial version of the database) would contain all the tables, relationships and properties required (done either fluently or using a chunk of sql in a script). When you want to push a change to a database, you would create a new

问题 Could someone explain the concept of Migrators (specifically fluentmigrator)? Here are the (possibly confused) facts Ive gleaned on the subject: Is it a way to initially create then maintain updates for a database by way of versioning. The first migration (or initial version of the database) would contain all the tables, relationships and properties required (done either fluently or using a chunk of sql in a script). When you want to push a change to a database, you would create a new

问题 For a project I'm currently working on I need to implement object versioning. Unfortunately I need to keep a full history of each object, so a single table solution like Papertrail would quickly become un-manageable. There are features of Papertrail which I like, however, which I haven't been able to find in a solution with individual tables for each model (such as acts_as_versioned). Ability to store meta-information from both controller and model Data is serialized so schema changes don't

问题 Would the following be a viable strategy for implementing versioning(using "example" as a sample document type): Have one original document where the type field is named example_original. Subsequent changes to the document all have type example_change and the id of example_original document as a key. The change would also carry a timestamp. Keep one doc with type example_current that is the result of example_original with all example_change "applied". A new example_change document would

问题 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

问题 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

问题 In our project we have several production databases and many devs. Each production database represents some "sub-project/localization version". We use SQL Server 2008. So, I need to develop database versioning strategy using MS Visual Studio Database Project. I have read a lot of articles about database versioning and database projects, but I still have a lot of questions: How developers should implement theirs changes to db project? (Best practice) How to generate the 100% workable "latest

问题 Consider the scenario: A Db transaction envolving more than one row from different tables with versioning. For example: A shopLists and products. Where a shopList may contain products (with their amount in the shoplist) and products have their current stock. When I insert ou edit a shopList, I want the stock of those products in the shopList to be updated to keep the stock consistant. To do that, I open a transaction, insert/update the shopList, update the stocks for each product (apply delta