On 20-Mar-09, at 3:15 AM, Fabio Natali wrote:
> However, on updating the website, I must be very *careful* and run a
> selective update/merge: I must not overwrite the data.db file which is
> on the web server and actually the most important piece of the story.

Best practice imho is not to use SQL lite for anything other than  
quickly playing around. I would strongly recommend postgres (other  
people my recommend others).

If i need to move data between database I do psql dumps and then  
import on the other server, but I think the idea of using SQL lite and  
keeping it SVN along with code is quite a fragile way to go.
--
   Andy McKay
   Clearwind Consulting: www.clearwind.ca
   Blog: www.agmweb.ca/blog/andy
   Twitter: twitter.com/clearwind


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to