6 ms·
That's not a very useful comparison. Databases are made to execute queries, not to install them. The only useful metric is performance and features (and price,
by vbezhenar 6y ago
That's not a very useful comparison. Databases are made to execute queries, not to install them. The only useful metric is performance and features (and price, of course). Sure, Oracle is bloated and pain to manage, but if it works faster, provides unique features and costs less in the end, people will use it.
- NOGDP 6y ago> Sure, Oracle is bloated and pain to manage, but if it works faster, provides unique features and costs less in the end, people will use it. _if_ Of course, those aren't the only reasons, and probably not the the main reasons, why big orgs use bloated proprietary crapware.
- koolba 6y ago> That's not a very useful comparison. Databases are made to execute queries, not to install them. The only useful metric is performance and features (and price, of course). Sure, Oracle is bloated and pain to manage, but if it works faster, provides unique features and costs less in the end, people will use it. Initial installation may not matter much but long maintenance windows directly lead to higher costs. If every patch requires a 60-90 minute downtime, you're going to pay for that in production deploy time.
- vbezhenar 6y agoThat depends on a service. For example I'm working on a service which is used by people at working hours (something like 8AM - 19PM, Mon-Fri). I can do anything outside of that window (well, +-30 minutes just to be sure) and nobody's going to pay for it, most likely nobody would even notice. And for service that's expected to work without interruptions, I think, there should be a way to switch to a secondary database, otherwise those promises are futile. And if there's a way to switch to a secondary database, long patch install time is not a big deal. Because whether it's 1 minute or 60 minutes, it's interruption nonetheless.
- Someone1234 6y agoRight but by that metric Oracle is archaic. Just look at Postgres[0] supported column data types and then look at Oracle[1]. Better data types means more tightly defined columns, which means fewer bugs/less defensive programming/reduced maintenance/reduced code complexity. No doubt someone will be along shortly to tell me "you don't NEED it!" and then tell me how to hack constraints into making it act like something it is not, but I don't care. I have no interest in "forcing" Oracle to act like a modern database through repeatedly having to re-define 30+ year old common data types (e.g. Int32, Int64, Long, Bool, etc). As a developer I /hate/ working with Oracle. It is just cludgy. I don't care how many times people point to vague indefinables for why it is "superior," it sucks to work with. Microsoft Sql Server is better, and Postgres/Sqlite are superb. Just the fact Postgres has a date (with no-time) column means it outright wins. In Oracle, we stored them as <Date> 12:00 but that's a gotcha since it can get timezone adjusted in the pipeline (e.g. <Date> 12:00 becomes <Date> 08:00) and the result be subtly broken. Cannot time-zone adjust a real date type. [0] https://www.postgresql.org/docs/9.5/datatype.html https://www.postgresql.org/docs/9.5/datatype.html [1] https://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#CNCPT012 https://docs.oracle.com/cd/B28359_01/server.111/b28318/datat...
- z3t4 6y agoYou should store dates with timezone or you can't make calculations like how old is this post. You could base it off system time, but then the calculation have to take into account summer/winter time.
- Someone1234 6y ago> You should store dates with timezone or you can't make calculations like how old is this post. I think you misread the post you responded to. It is discussing the benefit of Date Vs. DateTime data types. In Postgres, by design, a date has a 1 day resolution (i.e. no concept of hours/minutes, within that date). This is hugely useful for scenarios where you intentionally want and only want a 1 day resolution. It not being timezone adjustable is a feature, not a bug. Storing a DateTime with 12:00 and then an offset of e.g. 0, is a needlessly complicated work-around when a data type that doesn't even have the concept of hours or timezones exists.
- hartzell 6y ago> Databases are made to execute queries, not to install them. But being able to freely/quicly stand up database servers and quickly create/drop databases makes development and testing much simpler and more reliable. Given the question: "How do you know that deploying this thing will work?" - When it's quick/legal to stand up fresh servers and create databases, the answer can be "I tested it, just now, and it works." - Otherwise you end up in "I read through it and it looks good" or perhaps "We tried most of it on the test instance last week before the other team started using it." I much prefer the former.
- miahi 6y agoActually, the whole "create database" is misleading when comparing the two. For Oracle, a "database" is the a server instance; you create the database when you install the software (without creating a "database" you don't actually have anything running). For postgres, a database is just a level of data organization/segregation. In an oracle instance you only have a single database. The equivalent of the postgres "database" would be "user/schema" in Oracle.
- leandrod 6y agoNot at all. Because Oracle does not have multiple databases per instance does not equal a PostgreSQL database to an user in Oracle. On the contrary, it means PostgreSQL is way more flexible, because there we have and databases, and users and schemas as ISO meant it.
- wbl 6y agoOracle has the De Witt clause. If they had better performance would they have that clause?
- vbezhenar 6y agoOne of the reasons for this clause might be the fact that proper benchmarking is hard and wrong benchmarks might hurt sales.