3 ms·
Keep us posted on the performance issues you experience-- the team hangs out on IRC (#rethinkdb on freenode) and are usually more than happy to help work throug
by mglukhovsky 13y ago
Keep us posted on the performance issues you experience-- the team hangs out on IRC (#rethinkdb on freenode) and are usually more than happy to help work through these problems. If you identify a specific query that isn't performant, please open an issue on Github as well (http://rethinkdb.com/docs/comparison-tables/ http://rethinkdb.com/docs/comparison-tables/).
Also, RethinkDB 1.8 (shipping next week) will include native date support. You can follow the progress and discussion of the planned interface here: https://github.com/rethinkdb/rethinkdb/issues/977?source=cc https://github.com/rethinkdb/rethinkdb/issues/977?source=cc
- andrewmunsell 13y agoGreat. I've been meaning to jump on IRC with some questions, but haven't had the time to do so yet. I'll definitely be waiting for 1.8.
- EugeneOZ 13y agoAnyway timestamps are better. First reason is difference in implementations of "date"-formats in almost each database, and second reason - integers will always faster than strings or structures.