Rename of internal (OLTP) "Job" tables and columns
See original GitHub issueMigrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2079
Originally created by @DouweM on 2020-05-29 15:15:14
- Rename
job
table torun(s)
- Rename
job_id
column tojob_name
Note: Since the concept of ‘job’ itself is changing, we should either wait until #2924 is shipped - or else combine this with that.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
20 Managing Tables - Oracle Help Center
Tables are the basic unit of data storage in an Oracle Database. Data is stored in rows and columns. You define a table...
Read more >Change Data Capture Tables (Transact-SQL) - Microsoft Learn
Change Data Capture Tables (Transact-SQL) ... Returns one row for each change made to a captured column in the associated source table.
Read more >MySQL 8.0 Reference Manual :: 15.12.1 Online DDL Operations
Once the data is completely copied to the temporary table, the original table is renamed with a different temporary table name. The temporary...
Read more >Using data manipulation language (DML) | BigQuery
After a previous job finishes, the next pending job is dequeued and run. Currently, up to 100 INSERT DML statements can be queued...
Read more >Creating a SQL Server audit using SQL Server Change Tracking
And due to the fact that the internal tables are not visible and cannot be queried directly, you can take benefits from the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@tayloramurphy - What do you think about next steps here and priority level? It was in
Iteration 3
(passed) and I’ve moved toIteration 6
(early July) - feel free to adjust as appropriate.@tayloramurphy thanks for the confirmation – I see now that I actually responded in that thread, I must have just had some Github-migration-induced amnesia when going through 2.0 issues.