On 15 jan, 17:17, kaskado <jonlavi...@gmail.com> wrote:
> Hi,
> not sure the subject said exactly what I want but I tried ;) I'm not a
> web app/django expert so I hope you'll understand our problem.
>
> Let me first describe our system very quickly :
> -On one side we have customers publishing content (text + images)
> -On the other side, consumers, seeing and using this content
>
> When a customer publishes content, we want to approve it before the
> content goes live to Users
>
> Until there... fine ;)
>
> However, when content has already been published, the customer can
> still modify it. When a customer make a modification, we want to
> approve that before the modification goes live.
>
> I wonder how are we supposed to treat that :
> - Do we store the edited data separately until it is approved ? (we
> want the customer to see his non-approved edited data in his view,
> while the consumer sees the approved data)
> - Do we use 2 databases, like one would use 2 branch codes with
> release and development..
>
Definitively the first, as far as i'm concerned.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
