Hacker News new | comments | show | ask | jobs | submit | lneves's comments login

There is MonetDB: https://www.monetdb.org/

I use it with great success.


And it's been around forever. If you're interested in high-speed processing, there's lots of good papers from that project (e.g. how to avoid creating branches, stuff like that).


You can also add Duda.IO to the list: http://duda.io/


Oh yeah. Duda.IO totally rocks! Used it, love it!

Psst: There are very nice improvements coming to that project …


Can you give us some detail on what are those command-line switches?


See the docs for:

citext: http://www.postgresql.org/docs/9.2/static/citext.html

unaccent: http://www.postgresql.org/docs/9.2/static/unaccent.html

I think you can make it work.


I've been using postgres for a few years now, I also use MSSQL, MonetDB and MySQL.

Some of the things I miss most frequently are:

- Easy table partitioning.

- Support for "phrase search" in fts.

- MERGE/UPSERT support.

- Columnar storage (and related optimizations) for "OLAP like" workloads.

- EXPLAIN ANALYSE that traces functions.


We migrated recently from M$ $QL to postgres and are VERY happy with this move.


> M$ $QL


Heh, hopefully you're consistent and have similar antics for the likes of Apple, Google, et al


  find . -type d
edit: for the same output as your command you can use:

  dir -l


<quote>simply because a row can't contain sub-arrays or hashes</quote>

This is not true at all. At least in PostgreSQL you can have arrays and hashes:




Have you actually looked at or used the array stuff in postgres? It's pretty horrible syntactically and worse, very explicit in it's recommended use.

"Tip: Arrays are not sets; searching for specific array elements can be a sign of database misdesign. Consider using a separate table with a row for each item that would be an array element. This will be easier to search, and is likely to scale better for a large number of elements."

Searching an array is a pretty common task, Mongo does really well in its ability to search into objects in a document.

I had to laugh a little at one of the sample queries:

SELECT f1[1][-2][3] AS e1, f1[1][-1][5] AS e2 FROM (SELECT '[1:1][-2:-1][3:5]={{{1,2,3},{4,5,6}}}'::int[] AS f1) AS ss;



Yes I've looked at them. I use them every day. The example you posted its difficult to parse because it deals with multidimensional arrays and also populating one in the inner query. The simple, and much more common case of one dimension arrays is very straightforward. Can you show me the equivalent in MongoDB?

About the performance/scalability warning; I don't deal with very large arrays, a couple hundred items max, and when using a GIN index over the array field, search queries are screamingly fast.


Sure, check out:



I do not think that this is equivalent, it looks like querying complex JSON objects and not "simple" arrays.

From the "Array Element by Position" example:

  db.blogposts.find( { "comments.0.by" : "Abe" } )
PostgreSQL doesn't have JSON support but it does have XML/Xpath support.

If you stored XML documents in PostgreSQL the similar query to the MongoDB one would be something like this:

  select * from blogposts where (xpath('/comments[0]/@by', doc))::text[] = array['Abe']
Yes it's a little more verbose but not terrible so... at least in my opinion.


I would be interested to know if sports like cycling also have some kind of the negative health impact caused by the long periods of "sitting down".


yes and no.

Cycling puts an unnatural curve in our lower back, very similar to sitting in a chair, and due to the way the muscles work, cyclist end up with tight hip flexors and hamstrings and stretched spinal erectors (sorry, I've been out of Physiology for a while so can't remember the exact names of the muscles) which can further exacerbate the problem. Compare a cyclist with a runner, and you can see a noticeable difference in posture.

However, I wouldn't call it a 'negative health impact', as the activity is improving your health. Just be sure to stretch, and counter the muscle imbalances that the sport produces.

Many sports have similar results because they are unnatural. For example, snowboarders in big mountain areas end up with a unnaturally strong/tight oblique muscle on one side and one stronger leg. Surfers likely don't have this issue because the majority of their exertion occurs during the paddling phase and the length of time actually spent riding the wave is quite short.


I want to see it get out :-)


So the brain is, in a way, executing before the data is available (energy in this case).

You can absorb drugs on your mouth: http://silversol.110mb.com/use/sublin.htm

I would think that carbs are also readily absorbed in some quantity without the need of ingesting them.


Glucose, galactose and fructose are absorbed in the small intestine, although a small amount of glucose is absorbed through the mouth.





Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact