MongoDB Raises $150 Million at $1.2 Billion Valuation

Re:MongoDB Raises $150 Million at $1.2 Billion Valuation by ddorian43 on Friday October 04, 2013 @09:53AM (#6495336)

what are the data type problems?

[ Parent | on HN ]

Re:MongoDB Raises $150 Million at $1.2 Billion Valuation by rpedela on Friday October 04, 2013 @10:01AM (#6495387)

Support for arbitrary-precision decimal. Known as numeric/decimal in Postgres. This can be a problem for financial and scientific applications.

[ Parent | on HN ]

Re:MongoDB Raises $150 Million at $1.2 Billion Valuation by spongle on Friday October 04, 2013 @10:56AM (#6495700)

Yep we canned it because of that, plus it was unreliable and our code and architectural review scared the shit out of us.

[ Parent | on HN ]

Re:MongoDB Raises $150 Million at $1.2 Billion Valuation by jzwinck on Friday October 04, 2013 @10:00AM (#6495376)

Well, some of us have been asking for a native high-resolution time type for three years: https://jira.mongodb.org/browse/SERVER-1460

[ Parent | on HN ]

Re:MongoDB Raises $150 Million at $1.2 Billion Valuation by rudiger on Friday October 04, 2013 @11:20AM (#6495840)

Can't you just store it in a regular 64-bit integer and know it's a datetime from your application's logic?

What do you gain with a native, high-resolution datatime type?

[ Parent | on HN ]

Re:MongoDB Raises $150 Million at $1.2 Billion Valuation by bqe on Friday October 04, 2013 @11:43AM (#6495998)

Automatic timezone conversion and the ability to add and subtract dates without first dropping to your 64-bit into. Think DATE_SUB(date time, INTERVAL 1 HOUR) from MySQL for instance.

[ Parent | on HN ]