Update source_code field of dag_code table to MEDIUMTEXT
See original GitHub issueDescription
Update source_code field of dag_code table to MEDIUMTEXT
Use case / motivation
Lot of dags exceed the limit of 65K characters limit giving error "Data too long for column 'source_code' at row 1"
when enabling webserver to fetch dag_code from db.
Related Issues
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (8 by maintainers)
Top Results From Across the Web
changing fieldtype from TEXT to MEDIUMTEXT
Here is our table structure and sample data: ... This will change that custom field to MEDIUMTEXT, which will allow it to contain...
Read more >Change field in MySQL from TEXT to LONGTEXT
Simply go to table structure and change field type from TEXT to LONGTEXT . Or you can do it with this sql: ALTER...
Read more >Problem modifying column type from text to mediumText or ...
Another workaround that I`ve found. change the column to string (VARCHAR) type with the length of 70000 (or bigger than 65536) like this:...
Read more >Alter table change field to LONGTEXT; - Laracasts
Hello I tried to change Schema::table('table_name', function ($table) ... what I was trying to do is to change a text field (not string)...
Read more >Release Notes — Airflow Documentation
This table is synchronized with the aforementioned config values every time Airflow starts, and a new field log_template_id is added to every DAG...
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 Free
Top 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
Takes literally few minutes with Breeze: https://github.com/apache/airflow/blob/master/BREEZE.rst
“It’s a Breeze to contribute to Airflow!”
Again – this is only a problem for MySQL – PostgreSQL’s TEXT type can store 4gb
https://www.postgresql.org/docs/13/datatype-character.html
So your migration only needs to change it for MySQL.