Hi, On Thursday 22 December 2016 03:56:07 NoviceSortOf wrote:
> Our DB requirements though are complicated by the need to work with > Asian languages, Chinese, Japanese and so on as well as European > languages. This makes a relative import/export trivial between > various tables and is a major bottleneck. I don't get how languages tie in to choice of DB server software, other then "can it handle encoding X and Y". This you can research and for your own sanity, you may want to convert everything to UTF-8 before it enters the database. The cost calculation is simple: What can MSSQL do, that you actually *use* that others cannot. When you put the emphasis on feature use, a lot of propriety software becomes schockingly expensive and cheap to work around / do differently in perspective. -- Melvyn Sopacua -- 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/8566119.XPT6bmq6vq%40devstation. For more options, visit https://groups.google.com/d/optout.
