251–260 of 378 posts
Let's say migrating a multi node 10G RAC instance - what would I lose in terms of functionality - Distributed transactions, limitations on # of replicated nodes, RAT etc.
Just curious how far it has come in terms of replacing Oracle.
SQLite all over the place – it's great having a super portable DB format for quick little hits. There's nothing quite like sending a DB as an email attachment.
For me JSON has replaced SQLLite, with a large reduction in code and complexity. [ Admittedly I've written my own routines to access it more simply/directly on iOS ]
We use KDB+ for anything speed-critical - not on the lists, so I voted 'other'
Earlier quoted context omitted.
Amazon uses Oracle. I think to completely disregard Amazon because of this fact would be a mistake.
As does Facebook I believe
Earlier quoted context omitted.
SQLite is so pervasive that I'm pretty sure everyone uses it at some point. It's in client applications, it's used by yum (the package manager found on CentOS/RHEL/Scientific Linux systems), it's part of many web applications, it's part of many spam filtering systems, it's part of Android (maybe iOS, too?), it's basically impossible to avoid it if you're a nerd. Also, it's awesome.
Firefox uses it.
Earlier quoted context omitted.
SQLite is so pervasive that I'm pretty sure everyone uses it at some point. It's in client applications, it's used by yum (the package manager found on CentOS/RHEL/Scientific Linux systems), it's part of many web applications, it's part of many spam filtering systems, it's part of Android (maybe iOS, too?), it's basically impossible to avoid it if you're a nerd. Also, it's awesome.
Firefox uses it.
Earlier quoted context omitted.
For tabular data, relational databases rock. But the relational model doesn't align well with object-orientated programming so you have an ORM layer that adds complexity to your code. And with relational databases, the complexity of your schema grows with the complexity of the data. The graph-database model simplifies much of this and makes working with the modern-day social graph so much cleaner. Graphs allow you to…
> But the relational model doesn't align well with object-orientated programming so you have an ORM layer that adds complexity to your code. The mismatch comes about for a number of reasons: * OOP has no formal basis so it can't be reliably transformed into relational terms. * OOP is identity-bound -- each object is essentially an address in memory, not a relation in a set. * The biggie: OOP mixes data with behaviour…
Putting relational databases into their own group is silly. I believe this came about because relational databases have dominated for so long, and this has caused developers to try and fit every problem into the relational database model.
In the early days of the Web, choosing a database meant choosing between relational database management systems -- Oracle was king but expensive, Microsoft SQL Server if you were on a Microsoft stack, and PostgreSQL or MySQL were the primary open-source options (with one being a real RDBMS while the other was basically just an SQL interface to the file system).
Ten years ago the RDBMS was the only good option so that's what everyone used even though many problems and programming languages didn't match up well with it -- it was like trying to fit a square peg in a round hole.
You don't have to do that anymore so relational databases can stop being the one-size-fits-all solution, and instead we can move toward using them for the specialized cases where they're the right fit.
Earlier quoted context omitted.
Why do you use pgsql over mysql? I've used mysql a lot, and pgsql a little. I can't tell the difference, other than pgsql being slower and having less support. Some people swear by it, so I'm curious what I am missing.
I personally picked PostgreSQL instead of MySQL since I don't trust Oracle. Why support a free database server when it competes with Oracle RDBMS? Granted Oracle RDBMS is extremely expensive, but still, something doesn't sit well with me...
Is it possible HN has a very strong bias on web developers? Because in "serious business" or at least in my case in finance, you almost always find Oracle and DB2 being the leading DBs and maybe Sybase and maybe-maybe mysql or mssql but hardly ever postgre no matter how awesome it is and definitely never-ever something hip and cool and latest-fashion/fad like Mongo or Couch.