if one really wants to pay for suport you can still use postgres and pay to enterpriseDB
On Thu, Dec 22, 2016 at 2:45 PM, Sundararajan Seshadri <suns...@gmail.com> wrote: > The situation justifies the data base. There are more data bases (like > Oracle and Firebird) than what you have specified. But, let me compare the > ones you listed. Same observations apply to the other data bases too. > > On the first level comparison, you can say SQLITE is excellent for > productivity during development. It is also free. You can live with it if > only one or two users are likely to use the system. But if there are more > users or more entities (or tables), go for 'regular' RDBMS. > > If you are ready to pay consistent with the number of users (and get a > consistent support too!), go for MS SQL. But remember, MS SQL will also > mean more investment in terms of better hardware. (Note: There is a special > 'reduced' version of MS SQL which is 'free' can also be used. But remember > to read the licensing condition) > > If you want more than SQLITE but not ready to pay money, go for MySQL or > Postgre SQL. They are,by nature, without support (except among users, forum > etc.) but there are companies which offer paid support for these.) Either > of them is fine and almost they are replaceable by each other. But, > personally I would vote for Postgrew SQL since this is a little more > 'corporate' in nature. (Please do not fight with me - I love MYSQL too. The > comparison is like that between PHP and PYTHON. Again, I love both > languages!) > > I think there was a statement in Django documentation to the effect 'we > personally love Postgre!'. May be I am wrong? > > So back to my original reply: the situation decides what should be used. > > Food for thought: there are situations where RDBMS are not the best - and > they go for 'non-SQL Database'! > > ------------------------------------------------------------ > --------------------------------------------------- > > On Thursday, December 22, 2016 at 5:10:17 PM UTC+5:30, NoviceSortOf wrote: >> >> >> Curious what advantages if any people are finding working with DBs other >> than the default SQLLite? >> >> We are considering migrating to MSSQL to avoid kinks/ETL involved with >> having various DB backends for >> office and server applications, but uncertain the additional cost will be >> worth it or not. >> >> >> -- > 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 https://groups.google.com/group/django-users. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-users/64d650a0-6bc1-4259-8d08-063fbb66c231%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/64d650a0-6bc1-4259-8d08-063fbb66c231%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFWa6tJ%2B1suijBMF1rSwjCom_oFQuRsS25fbXdcddxNVS60cCw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
