taffer

14 ms·

121.
by taffer 5y ago
I thought that import substitution had long been discarded as an explanation for economic growth in Japan, Taiwan and South Korea. These economies were much more open than other countries at the time. A good counterexample would be Argentin
122.
by taffer 5y ago
> Jobs that were previously done by one person, but are now done by 10 people without an increase in measurable output. Is there any data to support this claim?
123.
A History and Evaluation of System R (1981) [pdf](people.eecs.berkeley.edu)
2 points by taffer 5y ago|0 comments
124.
DBOS: A Proposal for a Data-Centric Operating System(arxiv.org)
2 points by taffer 5y ago|0 comments
125.
by taffer 5y ago
Parent describes the experience and understanding of why certain methods of building software work better than others. A pattern, on the other hand, is more like a recipe that can be followed without knowing whether it is actually appropria
126.
by taffer 5y ago
This is essentially the idea of VoltDB [1]: All tables are partitioned and each partition is assigned to a single thread. As long as each query only touches a single partition, you get linear horizontal scalability and serializable isolatio
127.
by taffer 5y ago
The way you are supposed to use Postgrest or Postgraphile is to provide only views and stored procedures as the API. These views and stored procedures are layered over your data schema and should be the only way to query or change the data.
128.
by taffer 5y ago
Optimizability is one of the core ideas of the relational model. The others being data independence and a declarative query language. SQL is based on relational calculus and relational algebra, which in turn are based on first-order logic.
129.
by taffer 5y ago
In which cases are row-by-row loops clearer than set-based sql?
130.
by taffer 5y ago
Do you have an example of such a query? Maybe Common Table Expressions would have been enough instead of multiple roundtrips.
131.
by taffer 5y ago
If you don't trust abstractions to handle the inherent complexity of data processing, you won't get anywhere. If you ignore decades of database research, you'll just end up reinventing the wheel badly. What if you have a new
132.
by taffer 5y ago
These "complex monsters" are there to give you guarantees: Transaction isolation, referential integrity, constraints, durability, atomicity. A RDBMS is complex so your application can be simple. It takes care of things so you don&
133.
by taffer 5y ago
This concept of "public state" makes no sense to me. If the behavior of A, i.e. the implementation of A, depends on B, then changing the state of B will also change the behavior of A as a side effect. Otherwise, if B were "pu
134.
by taffer 5y ago
> That's not what encapsulation means Then what does encapsulation mean? If encapsulation means that an object protects all of its private state behind methods, then another object must not be able to manipulate that private state
135.
by taffer 5y ago
> Either this should be modelled so that A can directly reference C to start with, or indeed A has to go through B but can do so to get a reference to C (this does not break encapsulation in itself, it depends on the specific relationshi
136.
by taffer 5y ago
I try to put it another way, because it is a much more general problem of OOP: If you have an object A that references an object B and object B references C and A wants to know something about C, we always have to go through B, regardless
137.
by taffer 5y ago
> [...] an interface boundary that leaks no state is possible to implement and can give freedom to the designer regarding internal state. Your suspicion is justified. As long as the objects only send immutable messages to each other, enc
138.
by taffer 5y ago
OO aims at making future and unforeseen changes easier, I just don't think it achieves its aim. I am also not sure that a discussion on HN is the best medium to discuss the problem in depth. Nevertheless, I will try to give a practic
139.
by taffer 5y ago
Personally, I have come to the conclusion that object-level encapsulation is not a good design principle, but rather an antipattern because it complects data with code [1]. OOP tries to manage global mutable state by partitioning and encaps
140.
by taffer 5y ago
> If you don't want to use this system that makes it easy, fair enough. Be kind. Don't be snarky. Have curious conversation; don't cross-examine. Please don't fulminate. Please don't sneer, including at the rest
141.
by taffer 5y ago
It depends on your situation: If you already have a Postgres instance then the FDW is probably the easier solution.
142.
by taffer 5y ago
I havent tried it yet, but the parquet_fdw docs say you have to run ANALYZE on the table for optimal performance.
143.
by taffer 5y ago
Three reasons I can think of: - Postgres is a row store optimized for transactional workloads, whereas Parquet is a column-oriented format optimized for analytical workloads. - Database storage is typically very expensive SSD storage optimi
144.
Parquet foreign data wrapper for PostgreSQL(github.com)
1 points by taffer 5y ago|0 comments
145.
by taffer 5y ago
There is a parquet fdw for postgres: https://github.com/adjust/parquet_fdw
146.
by taffer 5y ago
Yes, filter_region, filter_supplier and order_column are parameters. The filter parameters are combined using AND, or if they are NULL, they are ignored. For example, you could set filter_region = 'Oceania' and filter_supplier = &
147.
by taffer 5y ago
Dynamic filtering and sorting can be performed using static SQL. In the following example the parameters :filter_region, :filter_supplier and :order_column are assumed to be defined by the user: SELECT * FROM example WHERE
148.
by taffer 5y ago
- You cannot have a good database design without understanding the business requirements first - Designing the code around the database leads to cleaner designs than doing it the other way around - Almost all columns should be NOT NULL - EX
149.
by taffer 5y ago
Suppose you create an API that allows users to enter nonsensical data or do things that are very bad for performance. Later, you realize your mistake, create a new, improved version of your API, and deprecate the old API. However, as long a
150.
by taffer 5y ago
Now you have your answer: Just instead of deploying to an app server you deploy to your db server. Yet for some reason people forget everything they have learned once the term SQL comes up.

More ›