On Monday, October 13, 2014 4:18:52 AM UTC-7, biuro wrote: > > > > perhaps I run out too far in the future and this should be put on a > different database. > what do you think guys? >
I think that database independence is a core feature of Django and of virtually every reusable app. Your project is designed (I assume) to be integrated into existing Django projects. By tying yourself to one database, your app is not being a good Django community citizen, and will be unusable by hundreds of thousands of existing Django projects that don't use postgres. If you find down the line that your app absolutely must have some pg-specific features, I recommend making those into *optional* features that can be enabled for qualifying users. ./s -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/1f8d0f7f-9e61-4fb4-ad7b-c5684cfab833%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
