-
Story for tech team to research and eliminate using 'dropTable' and use 'doTransaction' in DB migrations
Definition of Done
- [x] No new security vulnerabilities
- [x] Team code review
- [x] Docu…
-
Still does not
_Originally posted by @kamilsi in https://github.com/ttscience/unbiased/pull/55#discussion_r1490803442_
-
# Environment
Knex version: 0.19.3
Database + version: PostgreSQL 10.6
OS: alpine (docker image)
# Bug
We have an application that on every request it connects to a certain database. After …
-
There is no data storage technology endorsed by the repository template. There are options with trade-offs.
Some common directory names for the purpose of managing data storage creation, upgrades …
-
I'm used to the behavior in rails whereupon if you try to start your server and there are migrations that haven't been made to the database yet, the server will bail right away and tell you to go run …
-
i.e. assume that base schema corresponds to version X instead of "0". otherwise i'm not sure how should this be integrated with an application that has extant migrations.
my thought was to create m…
-
Currently when a planka database is created, or queried, knex defaults to using **public** as the schema name. Would it be acceptable to allow the possibility to pass a custom schema name through an e…
-
-
## Executing Migrator by having an ambient transaction.
I've been working on a feature to implement an all-or-nothing approach by using the migrator.
### Background
We have a multi-tenant appli…
-
### Required Terms
- [X] I agree to follow this project's [Code of Conduct](https://github.com/heroku/roadmap/blob/main/CODE_OF_CONDUCT.md)
- [X] I have read and accept the [Salesforce Program Agreem…