Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
michelpp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
39 ms
·
361.
▲
by
michelpp
8y ago
Nope, that's what views are for. https://www.postgresql.org/docs/current/tutorial-views.html
362.
▲
by
michelpp
8y ago
There are test frameworks for postgres. https://pgtap.org/
363.
▲
by
michelpp
8y ago
Views are the abstraction layer. https://www.postgresql.org/docs/current/tutorial-views.html
364.
▲
by
michelpp
8y ago
It's mysterious to you . For the rest of us is thoroughly documented: http://postgrest.org/en/v5.2/tutorials/tut1.html http://postgrest.org/en/v5.2/auth.html https:/&#x
365.
▲
by
michelpp
8y ago
Common orbits are solutions to the two body problem, but Shane Ross has a few videos on youtube about chaotic solutions to the three body problem, allowing objects to move in very complex orbits with very little fuel. This has been used fo
366.
▲
by
michelpp
8y ago
This is a good Javascript-centric writeup. This caught my eye thought: > Since JSON Web Tokens (JWT) are not signed using asymmetric encryption ... You don't have to, but can of course sign your JWTs with asymmetric keys, and many
367.
▲
by
michelpp
8y ago
Thanks for this link, very interesting talk from the graphblas author: https://www.youtube.com/watch?v=xnez6tloNSQ I've never seen any advantage to graphdbs over relational models until I saw this talk. Raising graph
368.
▲
by
michelpp
8y ago
> Also, GPUs are distinctively not systolic arrays. Hennesy's "Computer Architecture: a quantitative approach" has a good primer on Single instruction Multiple Threads (SIMT) architectures typically seen in GPUs. Good catc
369.
▲
by
michelpp
8y ago
Unpredictable performance would mean, you can't predict how long a specific query will take. This is the opposite of how postgres works. If a query is slow, it's predictably slow if the data doesn't change. So what you mus
370.
▲
by
michelpp
8y ago
You cannot be old-school and hype. That's the reason why it is old school. And the people who can't make good database design choices are exactly the kind of people who should be using SQL. Postgres knows how to optimize and pla
371.
▲
by
michelpp
8y ago
That, and simply reading the documentation. N+1 problems and denormalization-by-design are a failure to understand SQL.
372.
▲
by
michelpp
8y ago
You cannot have a local index for a FDW, how would it know to update when the foreign data changed? an approach you can take if you want indexed data from an fdw is to materialize the data (or a subset of it) and index that with 'CREA
373.
▲
by
michelpp
8y ago
The argument used by the author for 'abs' and 'min' can also be useful for all of the functions in the operator module: https://docs.python.org/3/library/operator.html In particular 'attrg
374.
▲
by
michelpp
8y ago
HyperLogLog, also by citusdata (no affiliation), is a great data type for statistically approximating counts of distinct values very quickly within an adjustable range of error: https://github.com/citusdata/postgresql-h
375.
▲
by
michelpp
8y ago
Great tip, minor point, did you mean 'returns setof fruits'? Otherwise your function will only return one row. Opinions vary but i think its another good argument for singular named tables as well: 'returns fruit' and &
376.
▲
by
michelpp
8y ago
That is what DISCARD ALL does, it discards all session state.
377.
▲
by
michelpp
8y ago
Writable views also work perfectly with PostgREST, if you're view is auto-updateable or has an INSTEAD OF trigger than you can POST/PATCH/DELETE via the view to mutate.
378.
▲
by
michelpp
9y ago
If you're using Postgres and want to get something done today, use PostgREST: https://postgrest.com/en/v4.4/ It is the fastest, leanest, and most powerful way to interface to postgres with an API. I've b
379.
▲
by
michelpp
9y ago
State machines also make excellent database constraints. Trigger based enforcement removes the need to implement machines in application languages and prevents bad code from inserting bogus states. This only matters if you're storing