-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trouble with virtual generated columns #338
Comments
You might be able to ignore the column in this function by removing the virtual columns from TableSchema.Table.Columns: ghostferry/table_schema_cache.go Line 205 in b3aaacf
|
That's a good thought, lemme pull on that thread locally and check back in! |
Sorry, I'm still struggling with this a bit, but hopefully will have an update in a few weeks! |
Ignoring in the table schema ended up being a bit of a dead end, it made the DML stuff pretty unhappy, in the end we settled with maintaining a |
Always interested in PRs - did you have some work in progress? |
I can try to untangle our change to get it into the upstream, we've had it in production for ~a year now, but our fork is so divergent it may not happen at this point D: |
👋 We have a virtual generated column, but it seems like ghostferry is trying to insert data into the virtual generated column when it should not, resulting in an error like...
Seems like we should just not insert any data into virtual generated columns
The text was updated successfully, but these errors were encountered: