Felix Zedén Yverås comments

Results 81 comments of


                                            Felix Zedén Yverås

Add `fold` option to avoid version code jumps such as v1.2.3 -> v8.6.3

I did NOT read the code closely enough when making these changes. Working on an actually working version.

Add `fold` option to avoid version code jumps such as v1.2.3 -> v8.6.3

Now it's fixed. As noted in my last commit, I have not added tests for the `fold` behavior. This is partly due to me not intending to spend this amount...

Cannot use `or_insert_with` for `HashMap::<usize, HashMap<usize, i64>>` - is this supposed to be supported?

Alright, thank you @clarfonthey ! I'm fine with closing this unless anyone wants to e.g. add an extra snippet of documentation somewhere or further discuss the "weirdness" of the `EntryRef`...

Cannot use `or_insert_with` for `HashMap::<usize, HashMap<usize, i64>>` - is this supposed to be supported?

I guess I would have liked to see a reference to `entry()` in the `entry_ref()` docs (and vice versa) with a short "use X instead if ...". To me, it's...

fix(node:http) dont delay for too long the first chunk, always set headersSent after end

I tested the version of bun from build 3047 and can confirm it passes the test I wrote. It still does not appear to work properly with testcontainers (#13696), exhibiting...

fix(node:http) dont delay for too long the first chunk, always set headersSent after end

@cirospaciari I'm available on discord if you want to compare notes - currently waiting on 3109 to complete building to test. **EDIT** Still seeing issues in 3109 :/

Support custom `CREATE DATABASE` statements

Additional use case: ```sql CREATE EXTENSION IF NOT EXISTS "postgis" ``` requires superuser, which my graphile user does not have. I can work around this by granting the graphile user...

Feature request: `compile` and `run` should be able to `--!include` fixtures

The reason I noticed this is because I prefer `graphile-migrate run ./migrations/current.sql` over `watch` as I don't want to run semi-completed statements accidentally. I also don't want to mess with...

[Feature] Allow one way relationships between stored procedures and tables

Are stored procedures (especially with parameters) supported at all at this point?

[Feature] Allow one way relationships between stored procedures and tables

Adding a note for future googlers: [Stored procedures are not supported by all database types yet](https://learn.microsoft.com/en-us/azure/data-api-builder/known-issues). See also #1023 , #1024 , #1500