On 2016-12-22 03:56, 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.
If you are genuinely interested in MS-SQL Server, I would spin up a simple test server and bang against it. Especially when it comes to these international characters. I've had issues with how it treats Unicode regardless of my settings and encodings (UTF-8 and UTF-16 can get truncated mid-sequence, spotty support for anything beyond 16-bit character ranges, tooling support for such characters, etc). If you're willing to treat your strings as opaque binary blobs and do all your character translation in Python, it's a little less headache. I used to be more vociferously against MSSQL due to its lack of OFFSET support, but have since learned that OFFSET is almost always the wrong solution and keysets+indexes almost always offer a more performant (and reliable) solution. So while OFFSET is nice for dev/testing, I now try to avoid it in production. While MSSQL has some great features, my only reservations now boil down to licensing: both in terms of monetary cost (especially when scaling) and availability of F/LOSS connectors. It can be done, but make sure that the benefits you receive are worth those costs. I wouldn't touch MySQL with a 10-foot pole thanks to Oracle. Its sister MariaDB (MySQL-minus-Oracle) has a few benefits, but more weirdnesses than I like to have when entrusting it with my data https://grimoire.ca/mysql/choose-something-else As others have mentioned, sqlite is great for local dev work, but doesn't scale as well. The classic "sqlite is a replacement for fopen()" is a good reminder. -tim -- 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 [email protected]. To post to this group, send email to [email protected]. 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/20161222090316.05292535%40bigbox.christie.dr. For more options, visit https://groups.google.com/d/optout.
