Hi Andy! Thanks for your kind reply. Andy Mckay wrote: [...] > 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).
- I'll manage quite a small bunch of data, say personal informations for a few hundreds people - I'll neither have special performance requirements, nor perform too complex queries - dealing with an "all-in-one-file" db may look handy: to perform the backup I simply copy one file That's why I thought of sqlite as a suitable solution to my needs. However, keeping the db under svn along with the code turns out to be troublesome. Given that performance won't be a worry, are there any other reasons why you would avoid sqlite? > If i need to move data between database I do psql dumps and then > import on the other server, Suppose I decide to use Postgres instead of Sqlite, do you have any tips on how to perform a backup of my data? Should I go for a psql dump? Thank you very much, -- Fabio Natali --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
