On Thu, Jun 3, 2010 at 6:31 PM, kakarukeys <kakaruk...@gmail.com> wrote: > I am developing a django web app which does some web publishing > (pushing some data to website). My customer is already using > ExpressionEngine 2.0 for publishing, hopes that I can reuse the CMS > for any publishing purpose. They does not wish to redevelop the web > publishing platform in Django. > > I'm asking if it is safe to... > > use the technique documented in > http://docs.djangoproject.com/en/dev/howto/legacy-databases/ > > to create models and do publishing using the models. So we will have > two web apps being able to access / query the database at the same > time. Will it cause issues like data corruption, etc?
It should be entirely safe. You'll have the same transaction and consistency issues that exist whenever you have two clients attached to the same database, but that's just due to have two clients talking to the same database -- you would get the same problems if you had two EE users attached simultaneously. The only other potential risk is if you have large amounts of data consistency logic implemented in user code under Expression Engine. In this case, you will need to duplicate this logic on the Django side, and there's the risk that you might introduce errors as a result of inconsistencies between the two implementations. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
