sendob
Joined 13 years ago
Joined 13 years ago
I think the response from amazon was fine and they are clearly not amateurs technically, communication was very poor.
Even a perfect database, should such a thing ever exist, is not sufficient to protect us from a determined disaster
With postgres and mysql you can find many companies competing to offer great service, and who can contribute their fixes and improvements directly should they so choose. The stronger the output of these communities and the organizations that support them, the more pressure for even the companies like Oracle to improve ( or perish :))
I prefer to work with Postgres when I can, but I also have found instances where MySQL better fit my needs, a heap table, even with more recently added index only scans ( and even reordering the table with cluster may not be desirable) you may want an index organized table (oracle term ) (mysql would say clustered index )
I am curious why even in the context of freely available engines we focus on competition, which I think can lead to great things, but I don't understand the animosity the communities feel towards one another, isn't it just a matter of horses for courses? Are we really interested in competitive kills or improving both the tools we use and our understanding thereof ?
I don't mean to single your comment out gbog, and I know this is certainly not exclusive to databases either ( witness almost any discussion of various programming languages on HN )
The lack of limit sucks, but the thing that annoys me most regularly is that Oracle refuses to make the 0 length string / null behavior configurable to allow for ANSI compliance ( MySQL null handling is worse IMO, makes me insane.... )
There was a time when vision correcting glasses were considered very strange I would imagine, but they proved to be very useful and we become accustomed to seeing them. What will be fun, I think, is as others have postulated wearable tech becoming less apparent to the naked eye, so much so that the plastic brick will be considered odd, and that one would WEAR vision correcting lenses mounted in metal or plastic frames right on the face?!
RE: circumventing the blacklist, I think immediately of accessing a function with postgresql aka select my_destructive_function();
Adoption was good especially for simple queries, people were less focused on the language, and more focused on exploring/modifying examples.
For people who are already familiar with SQL and as you said, less interested in the query language, it may be almost immediately frustrating.
I can absolutely see circumstances where it would be overkill, I have never tried to use it as a performance critical tool, just as more an easy thing to slap on to ease access, two aspects that I have found useful on more than one occasion:
1. HTRAF toolkit is convenient for very basic visualization (depending upon the audience this can be very useful to have at hand quickly)
2. multiple output formats (json in particular) has been helpful in terms of quickly hacking together prototypes in the past
Another tool, different, but also great for sharing, you may enjoy: http://htsql.org/
One phrase I remember from Cantrill re: Oracle & Solaris was that "People Innovate, not companies". Commits contribute, blog posts rarely do.
http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MySQL....
On Postgres, you could use arrays: http://www.postgresql.org/docs/9.3/static/arrays.html also has some great contrib modules as well like: http://www.postgresql.org/docs/9.3/static/intarray.html
Mongodb documents their multikey indexes for a similar approach: http://docs.mongodb.org/manual/core/index-multikey/
not to take away from rethinkdb, awesome to see a project move rapidly!
"In deployment, a routing layer handles routing requests from a public-facing hostname to the port-bound web processes."