Dominykas Mostauskis
Dominykas Mostauskis
Note that this is done by caching metadata. ## Checklist - [ ] My pull request has a descriptive title (not a vague title like `Update index.md`). - [ ]...
## Problem We have some sequences of commands that every developer has to run at one point or another. For example, for first time setup you run: ``` > cp...
Functions API's DBFunctions are used to build and represent SQLAlchemy expressions and are used, for example, for the frontend to describe row filters. The functions API JSON syntax (that describes...
## Problem The functions API lives in the db layer, and we want to use it by specifying columns via their Django IDs, which is a mathesar layer concept. To...
This is a low urgency problem. More like something to digest concerning frontend reactivity. In [this PR](https://github.com/centerofci/mathesar/pull/627#issuecomment-917023226) we ran into a bug where a derived store was calling its update/invalidation...
Branched off of https://github.com/centerofci/mathesar/issues/1368. Our test suite is burdened by test coverage having a lot of overlap. In other words, we often test the same thing multiple times, in multiple...
Branched off of #1368. The concern here is finding (and removing) state carry-over between tests (tainted fixtures). We take care to teardown and rebuild fixtures between test runs, but we...
Branched off of #1368. Fixtures are burdened by lack of coherence. We want better names, better namespacing, more predictable hierarchy, more reuse.
Branched off of #1368. We currently spin up new SQLAlchemy Engines whenever, which has a lot of overhead. Also, in testing this creates too many database connections (each Engine has...
My introduced exception classes seem more generic than the rest. I think it works well in this case, but I'm open to other suggestions. ## Checklist - [x] My pull...