search

ShuffleBox / django-rcsfield

Automatically exported from code.google.com/p/django-rcsfield
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

format db field based on RCS format #13

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
when i first heard RCSField I thought it was a django model field that 
maintained it's content in RCS 
format behind the scenes in a large text field.  So you could use any version 
from the "rcs enabled" 
field.  Maybe this is a good idea, or in the scope of this project, so the 
additional requirement of 
having to configure a version control system for lets say one field in your 
database, is eliminated.  
Would be helpful for me anyway. :D

I was looking around to find an example of what an RCS field formatting looks 
like and this is what I 
came up with ... 
http://www.networkcomputing.com/1221/1221f46.html

Original issue reported on code.google.com by mand...@gmail.com on 22 May 2009 at 8:22

GoogleCodeExporter commented 9 years ago 
First let me say I like the idea.

I have to think about it a bit before a decision will be made. The parsing of a 
big
history might get slow and the db will grow in size over time, so there are not 
only
advantages.

If you don't want to configure anything just don't use the svn backend. Bazaar, 
Git
and Mercurial backends are fully managed by django-rcsfield and don't need any 
setup
by the user.

Access to older versions is also possible with the current implementation, so 
the
only advantage of storing RCS-Format in the Database would be that all history 
is in
the db itself. If this is the only goal django-reversion might be a good 
choice.

Original comment by a...@rcs4u.de on 23 May 2009 at 7:23

GoogleCodeExporter commented 9 years ago 
Well problem is I am not very familiar with Bazaar, GIt or Mercurial.  So my 
only real option is svn to minimize 
complexity into the project.  I might look further into the svn option, it's 
probably not much work/ too horrible a 
dependency and one should be maintaining their own version control system if 
they are writing software.  Right 
now we are just using google code but I am being lazy to not setup our own svn 
server even if it's initially used 
only for the CMS. ;D

Original comment by mand...@gmail.com on 28 May 2009 at 2:35