Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
yrashk
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
Show HN: Cognitive Layers
(github.com)
3 points
by
yrashk
6mo ago
|
0 comments
2.
▲
by
yrashk
6mo ago
I've been working on some parts of this problem, specifically capturing and retaining other semantically useful layers of the systems we build as we build and maintain them. By introducing progressive semantically enriching layers (sta
3.
▲
by
yrashk
6mo ago
Relax NG Compact is a great way to communicate schemas to LLMs in a token-efficient way.
4.
▲
We Forked Supabase Because Self-Hosted Postgres Is Broken
(vela.simplyblock.io)
9 points
by
yrashk
7mo ago
|
1 comments
5.
▲
Inferal Workspace Architecture: How We Work at Inferal
(gist.github.com)
1 points
by
yrashk
9mo ago
|
1 comments
6.
▲
by
yrashk
9mo ago
This document describes the conceptual architecture of our company workspace - a text-based, version-controlled knowledge and operations hub designed to replace tools like Notion and Webflow while being natively accessible to AI assistants.
7.
▲
by
yrashk
11mo ago
This happened to FerretDB
8.
▲
by
yrashk
1y ago
seemingly only for domestic R&D
9.
▲
by
yrashk
1y ago
As an international founder, I'd like the section 174 to be fully restored as it was before – not just for domestic R&D but offshore one as well, so we're not hit with 15 years deprecitation (it is as good as "infinity&qu
10.
▲
by
yrashk
2y ago
This is the first _published_ version: https://docs.omnigres.org/omni_txn/linearize/
11.
▲
by
yrashk
2y ago
Please bear in mind that it's not a final version yet – it is a snapshot from a PR. Few more cases are being worked on!
12.
▲
Troubleshooting SQL Queries with omni_id
(blog.omnigres.com)
2 points
by
yrashk
2y ago
|
1 comments
13.
▲
by
yrashk
2y ago
The article describes a technique type-safe joins in Postgres.
14.
▲
by
yrashk
2y ago
Current image builds are to be phased out soon(ish). They were a way to get something into people's hands. And yes, plrust/rust are definitely space hogs :)
15.
▲
Troubleshooting SQL Queries with Omni_id
(blog.omnigres.com)
1 points
by
yrashk
2y ago
|
0 comments
16.
▲
by
yrashk
2y ago
I've been a user since the early days and loved the immediacy of responses to all our issues. Issues were fixed nearly instantaneously. It's very impressive. Yet to explore the new capabilities!
17.
▲
by
yrashk
2y ago
As somebody who writes a lot of Postgres extensions, I can say this is quite interesting! I think I can see some parallels to Supabase's wrappers project. Keep up the good work!
18.
▲
by
yrashk
3y ago
Omnigres | Founding Engineer | SF Bay Area HQ | REMOTE At Omnigres, our north star is to enable developers to laser-focus on business needs instead of fighting technological challenges. We're fighting the complexity and inefficiencies
19.
▲
by
yrashk
3y ago
We are primarily talking about the backend side of this story at this time. We'll see what the future will bring, as the real edge of computing is in user's hands. There's a keen interest to get there for Omnigres application
20.
▲
by
yrashk
3y ago
We're experimenting with JSC.
21.
▲
by
yrashk
3y ago
It does not have any UI yet. Something we haven't thought much about yet. Technically, feasible, just need to have a good story to drive a good experience there.
22.
▲
by
yrashk
3y ago
Currently, we have an early version of `omni_schema` [1] that allows traditional incremental migrations and in-place migration of certain objects. However, we're not quite satisfied with this and working on a more sophisticated system
23.
▲
by
yrashk
3y ago
We are working on first-class support for Python indeed (and other languages like JavaScript) An important thing here is that we see Omnigres as a polyglot runtime with a database inside (Postgres) and we want people to use languages they p
24.
▲
by
yrashk
3y ago
In my tests, I was testing against Node.js and Rust and was getting roughly the same numbers. https://yrashk.com/blog/2023/02/16/what-happens-if-you-put-h... In the instance of short-living queries, we a
25.
▲
by
yrashk
3y ago
Interestingly enough, I've toyed with augmenting SQL to make it more useful. I remember doing an experimental improvement allowing to do FROM where SELECT what syntax. I agree there's value there. Omnigres is able to intercept que
26.
▲
by
yrashk
3y ago
That's right. This is on our near-term roadmap at Omnigres.
27.
▲
by
yrashk
3y ago
You can use any language Postgres supports or will support to write your logic. We are adding first-class Python support right now. It's already possible to extrsct stored functions from decorated functions and their type hunts and we&
28.
▲
by
yrashk
3y ago
Thanks! I am pleasantly surprised my name rings the bell for some :)
29.
▲
by
yrashk
3y ago
We're actually first-classing a number of languages and ecosystem support precisely so that people can use their languages of choice and not just SQL or Pl/pgSQL.
30.
▲
by
yrashk
3y ago
Thank you for posting Omnigres on HN! Just a quick note to the readers: we're still in the early days, in a pre-release mode. A lot of things work, but not everything is there yet and there are some bugs (we know some for sure!). A lot
More ›