Loading problem...
A payroll data pipeline stores employee compensation records in a Salary table:
A downstream integration expects the opposite marker convention, so every row must be transformed as follows:
Return a transformed result table with exactly these columns:
Additional requirements:
Supported submissions:
Salary:
| id | name | sex | salary |
|----|------|-----|--------|
| 1 | A | m | 2500 |
| 2 | B | f | 1500 |
| 3 | C | m | 5500 |
| 4 | D | f | 500 |[
{"id":1,"name":"A","sex":"f","salary":2500},
{"id":2,"name":"B","sex":"m","salary":1500},
{"id":3,"name":"C","sex":"f","salary":5500},
{"id":4,"name":"D","sex":"m","salary":500}
]Explanation
Each row is transformed independently by flipping sex code m<->f while preserving all other columns.
Salary:
| id | name | sex | salary |
|----|-------|-----|--------|
| 11 | Nia | f | 8000 |
| 7 | Omar | m | 7200 |
| 15 | Leah | f | 8100 |
| 9 | Jonah | m | 7100 |[
{"id":7,"name":"Omar","sex":"f","salary":7200},
{"id":9,"name":"Jonah","sex":"f","salary":7100},
{"id":11,"name":"Nia","sex":"m","salary":8000},
{"id":15,"name":"Leah","sex":"m","salary":8100}
]Explanation
Input order can be arbitrary. Output must still be sorted by id.
Salary:
| id | name | sex | salary |
|----|------|-----|--------|
| 100 | Kai | m | 9000 |
| 101 | Kai | m | 9000 |
| 102 | Kai | f | 9000 |[
{"id":100,"name":"Kai","sex":"f","salary":9000},
{"id":101,"name":"Kai","sex":"f","salary":9000},
{"id":102,"name":"Kai","sex":"m","salary":9000}
]Explanation
Rows are not grouped or deduplicated. Every record is toggled independently, even with repeated names and salaries.
Constraints