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.
Hi,
I'm using SQLite in production in one application I've made for an eshop hosted
by BigCommerce. It gets the orders from the BigCommerce API and formats them on
a PDF for printing on labels. It has no models, and all the data is stored in
BigCommerce. The only significant data stored in SQLite
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
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 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
SQLite is very good for what it is and requires zero admin and no
installation, but it cannot scale, has no replication, and cannot run on
separate server.
Postgres has robust transaction DDL, which means that if you get a crash in
the middle of a migration the change gets reversed. MySQL does
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
https://sqlite.org/whentouse.html
SQLite is not directly comparable to client/server SQL database engines
such as MySQL, Oracle, PostgreSQL, or SQL Server since SQLite is trying to
solve a different problem.
Client/server SQL database engines strive to implement a shared repository
of enterprise
The primary cost is licensing unless we can scale the MS-SQL db projects
size and more expensive hosting cost .
Currently we use PostGresSQL, based in part of my suspicions of the
limitations of SQLite.
Our DB requirements though are complicated by the need to work with Asian
languages, Ch
I do not want to speak ill of sqlite, it is very useful for development,
testing and other uses, but in short it is not a fully featured DBMS.
Django can work with many different databases, not only sqlite and MSSQL.
You will have license costs for the database and for the OS, I would
personally
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.
10 matches
Mail list logo
