“What are common names for short database manipulation programs? Do you have a special name for programs that address errors or bulk changes in records? My team calls them Quick Fixes or Quickies – what about yours? #database #recordmanipulation #quickfixes #programmingtips”
## Identifying Short Database Programs
Understand the different names used for short programs that manipulate records in a database.
### Defining Quick Fixes
Learn about the concept of Quick Fixes and how they are used in database management.
### Naming Conventions
Explore various names that different teams use for programs addressing errors or bulk changes in records.
### Personal Experience
Discover how one team refers to these programs as Quick Fixes or Quickies, and the reasoning behind this choice.
## Engaging in the Conversation
Share your team’s unique name for these types of programs and contribute to the discussion within the programming community.
I think the word you’re looking for is “script”
migration script.
Also, you have snapshots and are not testing in prod, right? Is there no room for error? Does everything go to hell if you make a mistake? That’s terrible if that’s the case.
Like the other comment said, we just call them SQL scripts (or whatever type of database you use). It sounds like the ones you have to write are pretty complicated. We usually don’t do much beyond insert, update, etc. statements. Maybe your team calls them quick fixes because the computer runs them quickly?
[Data cleanser](https://en.wikipedia.org/wiki/Data_cleansing)?
You’re referring to SQL DML(Data Manipulation Language) scripts.
My old company we called them datafixes. They had a “restore” query that pulled in existing data in case we needed to revert back to that data, and the actual “datafix” query that change data. They ranged from simple 1 record updates, to more complex updates across several shards.
“Data patches”, DML scripts; if the data corruption is due to a programming error – we bundle them under bug fixes. i.e. the code and the “data utility” or “utility” bundled together to resolve the issue.
corrective scripts
We call them batch jobs
Alter
Crud?
My company calls them data fixes
we call it (data) Upgrade Process
Little Bobby Tables
oneoff
we call them migrations
Migration script
Adhoc scripts
Scripts, database scripts if we need to be more specific. “Quickies” is crazy tho
> Does your team have a special name for them?
Bugs.
A place I used to work referred to these as “one-times” or “one-time dml”.
Another place I worked called these “migrations” but also called schema changes / ddl “migrations” and also called moving off of an old 3rd party system to a new in house system “migrations” and also called rewriting pieces of functionality into a different stack “migrations”. Everything was migrations.
I liked one-times, because there was less ambiguity.
patches