Re:Why SQL is beating NoSQL, and what this means for the fut...
by collyw on Tuesday September 26, 2017 @03:17PM
(#15341678)
Creating an index in one command is a bonus of using SQL databases. Messing around creating yet another database seems to be the equivalent on NoSQL.
Re:Why SQL is beating NoSQL, and what this means for the fut...
by autokad on Tuesday September 26, 2017 @10:13AM
(#15338793)
you obviously have not used databases very much if you think you can join 2 billion row tables on a key that is not indexed in a reasonable amount of time.
Re:Why SQL is beating NoSQL, and what this means for the fut...
by testvox on Tuesday September 26, 2017 @12:27PM
(#15340158)
So? It's not like a nosql db without indexes will be any faster at it.
Re:Why SQL is beating NoSQL, and what this means for the fut...
by autokad on Wednesday September 27, 2017 @11:06AM
(#15348469)
yes, its absolutely faster. try it. Granted a nosql db like hive is 'cheating' by taking advantage of lots of disks/hardware on lots of machines, but i routinely join billion row tables with million row tables and wait only a minute.
Re:Why SQL is beating NoSQL, and what this means for the fut...
by taco_emoji on Wednesday September 27, 2017 @05:16PM
(#15352427)
> Granted a nosql db like hive is 'cheating' by taking advantage of lots of disks/hardware on lots of machines
That's not "cheating", it's literally the only relevant factor.
Who would win in a fight: a superintelligent ninja cat with laser nunchucks and body armor, or a dog?
Most (all?) RDBMS's have something like a varchar(max) which accepts reasonably large strings.
> you have to create indexes and fus with all sorts of relational nonsense
No, you don't.
> its going to read the entire table into memory and re-write it back to disk
Probably not, if you're adding a nullable column.