RedCrowbar

7 ms·

1.
by RedCrowbar 1y ago
Wine supports WoW64 since recently [1] [1] https://www.phoronix.com/news/Arch-Linux-WoW64-Wine
2.
by RedCrowbar 2y ago
You can use access policies [1] to emulate temporal data. See an example in [2] [1] https://docs.geldata.com/reference/datamodel/access_policies [2] https://github.com/geldata/gel/issues&
3.
by RedCrowbar 2y ago
Strictly speaking we charge for compute and storage. You can create variously-sized Gel instances and within those instances an arbitrary number of branches.
4.
by RedCrowbar 2y ago
The paper seems to mostly focus on the quality of cardinality estimation (mostly driven by statistics) which is admittedly one of the frequent sore points in Postgres. There's been some progress in that area though (CREATE STATISTICS
5.
by RedCrowbar 2y ago
That's already supported, you just need to set the Postgres cluster URI in the `GEL_SERVER_BACKEND_DSN` env var ([1]). [1] https://docs.geldata.com/reference/reference/environment#gel...
6.
by RedCrowbar 2y ago
You can use Docker (and Docker Compose) with Gel for local development [1], but of course you'd miss out on most management features of the CLI, because it's not built to supplant the docker/docker-compose CLI. Are there any
7.
by RedCrowbar 2y ago
(article author here) > If I use some other extension like timescale is that compatible with gel [...] Postgres is so powerful partly because of its ecosystem, so I want to know how much of that ecosystem is still useable if I’m using ge
8.
by RedCrowbar 2y ago
Gel as in gif obviously! :-)
9.
by RedCrowbar 3y ago
EdgeDB is NOT an object store. It is "relational model enhanced" instead where a set is a fundamental building block [1] so not just relations are sets, but attributes can be sets also. [1] https://www.edgedb.com/
10.
by RedCrowbar 3y ago
If your database client is any good, it should do the retries for you. EdgeDB uses serializable isolation (as the only option), and all our bindings are coded to retry on transaction serialization errors by default. Transaction deadlocks ar
11.
by RedCrowbar 3y ago
Yes. Apache 2.0 licensed with lots of focus on local-first development.
12.
by RedCrowbar 3y ago
There is a work-in-progress query builder support for .NET: https://github.com/edgedb/edgedb-net/tree/feat/querybuilder-...
13.
by RedCrowbar 3y ago
We wrote a blog post about this specifically: https://www.edgedb.com/blog/why-orms-are-slow-and-getting-sl...
14.
by RedCrowbar 3y ago
> Can EdgeDB solve the problems like `soft-delete`? Yes, with access policy rules. E.g global hide_deleted: bool; type SoftDeletable { deleted: bool; access policy hide_deleted allow all when (global hi
15.
by RedCrowbar 3y ago
The whole thing consists of these main parts: 1. SQL parser: https://github.com/edgedb/edgedb/tree/master/edb/pgsql/parse... 2. SQL transpiler: https://github.com/edgedb/ed
16.
by RedCrowbar 3y ago
No plans for that yet. We feel EdgeQL is a far superior choice for the intended use case of application development.
17.
by RedCrowbar 3y ago
Yes, although rewrites are fairly minimal. Mostly limited to name mangling.
18.
by RedCrowbar 3y ago
Yes, we are looking into possibly supporting in-place upgrades in future releases.
19.
by RedCrowbar 4y ago
Efficient transitive closure (aka link recursion) is something we plan to tackle soon (see https://github.com/edgedb/edgedb/discussions/2634 for some discussion on the topic).
20.
by RedCrowbar 4y ago
Yes: https://github.com/edgedb/edgedb-go/issues/182 Feel free to jump in with suggestions, we need feedback from experienced Go devs.
21.
by RedCrowbar 4y ago
EdgeDB does not use Postgres RLS, access rules are injected into every query by the query compiler instead. This side-steps the RLS gotchas and limitations (RLS does not allow aggregates in rules, EdgeDB does), but also yields somewhat bet
22.
by RedCrowbar 4y ago
Alas, we have to wait until CockroachDB becomes a bit more capable SQL-wise. I gave a more elaborate answer in https://github.com/edgedb/edgedb/discussions/3403 .
23.
by RedCrowbar 4y ago
With the addition of `GROUP` in 2.0, EdgeDB is as suitable for OLAP as vanilla Postgres is (unless you absolutely need window functions, which we don't implement yet).
24.
by RedCrowbar 4y ago
EdgeDB is very particular about how the underlying data is organized, so you can't put it in front of an existing database. Importing schemas and data is another story which we're working on.
25.
by RedCrowbar 4y ago
Only the query compiler is in pure Python and you only hit that once per query, as the compilation result is trivially cached. The hot path is a combination of Cython, C and Rust. We have a suite of benchmarks [1] that show relative overh
26.
by RedCrowbar 4y ago
I think the OP meant `NOT NULL` as in nullness check in queries. EdgeQL uses `exists <foo>` to check for existence of data. We have examples in the cheatsheet and elsewhere but it's probably hard to find if you're looking
27.
by RedCrowbar 4y ago
Yes, we'll be adding a way to choose the index type. It's even more relevant now that we've exposed range types.
28.
by RedCrowbar 4y ago
You can run the server in foreground [1] with `env EDGEDB_DEBUG_EDGEQL_COMPILE_SQL_TEXT=1` and observe emitted SQL. [1] edgedb instance start --auto-restart --foreground -I <your instance>
29.
by RedCrowbar 4y ago
Postgres does have a very elaborate extension system, but it's unsuitable for something like EdgeDB, because we are fundamentally altering the database interface: EdgeQL vs SQL and a different client/server protocol.
30.
by RedCrowbar 4y ago
That `sys::TransactionIsolation` doc is outdated, EdgeDB only supports the `Serializable` transaction isolation. See related discussion [1] At this point EdgeDB supports Postgres HA passively, i.e. it will react to a failover event in your

More ›