If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > General > Database Concepts & Design > Storing Versioned Data in Distributed DB vs RDBMS

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-23-11, 10:55
phreak3eb phreak3eb is offline
Registered User
 
Join Date: Apr 2011
Posts: 1
Question Storing Versioned Data in Distributed DB vs RDBMS

I'm not sure if this is the place for this post but I didn't really know what it fell under so I apologize in advance if this belongs in another forum.

I'm looking at creating a new online app for myself and others to store certain types of data. I'd like the ability to display this data in a "versioned" sort of way.

For example, someone uploads some data for people to use. Someone else comes along and likes what they did, but wants to modify it and store it under their collection as well, so they "fork" it. I want anyone to be able to see the changes in this data and view it in almost a Microsoft Word track changes kind of way (not just a compare versions sort of way).

I was looking at doing this using Google App Engine and Python but am curious if what I'm wanting to do would work in the type of DB GAE (distributed I believe) uses efficiently or if hosting it somewhere else and using a "traditional" RDBMS like MySQL would be better.

So what would be the "best" technology to do this with?
Reply With Quote
Reply

Tags
distributed, rdbms, versioning

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On