at the very least use mysqldump on you db or a table before you play with the code. though depending on what you are doing backup should be even more structured than ad-hoc sql dumps.
http://www.thegeekstuff.com/2008/09/backup-and-restore-mysql-database-using-mysqldump/ On Mon, Jan 17, 2011 at 10:45 PM, Vovk Donets <donets.vladi...@gmail.com> wrote: > > > 2011/1/17 ckar...@googlemail.com <ckar...@googlemail.com> >> >> Sry for the wrong url. It's now >> http://g2007.ch/media/static/uploads/django.pdf >> > > Great work, many thanks! > > -- > Vovk Donets > python/django developer > skype: suunbeeam > icq: 232490857 > mail: donets.vladi...@gmail.com > www: vovk.org.ru > > -- > 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. > -- 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.
