Please use neither. Reason is as number of lookups varies, you'll have to template query as a string adding either values to IN list or `OR` conditions. Not only it causes excessive string concatenation on your app side, these queries are also seen as distinct queries which has following drawbacks:
- every query has to be planned
- your DB driver can't prepare query as they are all different
- collecting per query stats becomes nightmare if number of arguments per query varies in wide range. metrics cardinality is a problem.
Correct way to handle it is pass all args as single parameter of type array and use `= ANY($1)` or if there are multiple columns build a virtual table and join:
SELECT a,b FROM table
NATURAL JOIN ROWS FROM (
unnest($1::type_of_a[]),
unnest($2::type_of_b[])
) t(a,b)
There was a company I can't recall its name, but they took VC funding for one round, retained voting control, built successfull business and then refused to go for another VC round. VC still owns company, but can't exit and founders are happy with the way things are.
Does ZFS or any other FS offer special operations which DB engine like RocksDB, SQLite or PostgreSQL could benefit from if they decided to target that FS specifically?
I like the appeal of model being bidirectional. Also modelling sequence of actions is really not solved problem in Terraform & Pulumi: canary change, check metrics, rollout to the rest of the region, check metrics, then all regions, if they solved it all while being "declarative" and high level it can be the next tool of choice for me.
I am not worried about UI representation of the model like many comments, it is not the main point of this project as I understand. UI just that - a representation, same relationships might as well be coded in HCL or the like of it.
There is still no good support for io_uring in Rust. AFAIK none of existing solutions fully support multishot ops, zerocopy ops with delayed buffer release, sending messages to another ring with IORING_OP_MSG_RING or convenient ops linking
If it was flying at 80000ft as initially reported, how did they shot it down? No fighter planes can fly that high. Did they wait until it lowered to the operating altitude?
Despite all the effort, benchrmak results are still not consistent. The other day I wanted to check how Ryzen 7600 compares to i13600k in code compilation. Ratio in time between these 2 processors reported by different authors were wildly different:
LTT: 129%
GN: 160%
Techpowerup: 105%
With results fluctuating up to 2 generational differences it is hard to make sense, despite all the authors effort. This leaves that kind of content more of entertainment rather than informational and from that perspective low effort doesn't bother me.
IPv6 only is still unusuable :( I bought new Sony TV and allocated it a new VLAN with IPv6 only network just to see how it works TV couldn't even detect that it connected to the internet, despite it receiving ipv6 address from my router. It looks like it couldn't use IPv6 DNS servers. If I try to configure IP address statically it wont let me enter IPv6 address at all.