You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the title says. Sometimes, in our tests, data is being inserted into real tables (outside Balta, e.g. a service test in which the server is sending data to DB via a DB layer), and it's a good practice to remove it.
Perhaps all the data from a table, perhaps only certain using WHERE clause (could be in another ticket if it's technically complicated on the first iteration).
Nevertheless, this feature is very good to have as it would make our interactions with DB in some tests easier.
The text was updated successfully, but these errors were encountered:
lsulak
changed the title
Feature request: add possibility to delete data from table
Feature request: add possibility to delete data from table (explicitly)
Oct 2, 2024
lsulak
changed the title
Feature request: add possibility to delete data from table (explicitly)
Feature request: add possibility to delete data from table (manually / explicitly)
Oct 2, 2024
benedeki
changed the title
Feature request: add possibility to delete data from table (manually / explicitly)
Add possibility to delete data from table
Oct 10, 2024
* add methods `delete` to `DBTable` in several overloaded flavors
* fixed `addNull` evaluation bug on `DBTable`
* added license entries to testing SQLs
* `DBTable` covered by integration tests
Background
As the title says. Sometimes, in our tests, data is being inserted into real tables (outside Balta, e.g. a service test in which the server is sending data to DB via a DB layer), and it's a good practice to remove it.
Perhaps all the data from a table, perhaps only certain using
WHERE
clause (could be in another ticket if it's technically complicated on the first iteration).Nevertheless, this feature is very good to have as it would make our interactions with DB in some tests easier.
The text was updated successfully, but these errors were encountered: