Tiji Mathew

Thank you @saperry for a creative use of the `-f` and `-m` options. Have you run into any SQL file size limits ? What was the largest sql file in...

Hello @CermitDFrog Could you look a the PR you raised and help us resolve the merge conflict with the latest version of Schemachange and help close this issue accordingly. If...

Interesting @MACKAT05. Using the Render to verify the sql that will be executed appears to be useful application of the `render` functionality. It is as if we need a `--dry-run`...

This appears to be a major refactor. Appears to be a 4.0 release candidate. Will get back to you @MACKAT05 once I have a chance to sync up with @jeremiahhansen.

@binitbhaskar, It does not appear to be a bug with schemachange. Schemachange is supported on python 3.8, 3.9 and 3.10. Your docker container seems to be running Python 3.12. Can...

@zanebclark Amazing work here. Will need to review and see if we can carve out the changes into multiple pull requests to be released without breaking previous patterns. For breaking...

> @sfc-gh-tmathew , apologies for the delay in my response. I'm embarrassed to have created such a behemoth. I've been eating my own dogfood by using this branch to create...

> If the "change_history_table" string is a schema and a table, use the "snowflake_database" instead of "METADATA" This will be a breaking change to existing end users for those users...

Hello @mhan92, Thank you for reaching out and attempting to solve for failed scripts logging. What are your current thoughts of logging failed scripts based on the latest v3.6.0. Do...

Hello @casba Thank you for reaching out. As @CermitDFrog pointed out, Schemachange is behaving as designed. I cannot think of a way to block a client connection from executing a...