Evan Elias

Yes, see 2nd bullet of the original issue text above :) The developer ergonomics with comments aren't great though. Overall this issue is pretty low priority, as the effort-to-reward ratio...

Sorry but only the InnoDB storage engine is primarily supported by Skeema at this time... this is noted in the [requirements doc](https://www.skeema.io/docs/requirements/#database-version-and-flavor). Most older storage engines (MyISAM, MEMORY, etc) tend...

No worries. Also just wanted to clarify this situation is a warning message (non-fatal / not an error) -- * Skeema skips attempting to ALTER unsupported tables, but other tables...

Thanks for the question. Sorry but this is not supported currently. A few related alternatives: * If it's fine/expected for some tables to violate a linter rule, be sure to...

This would be a bit complicated, due to how mid-statement SQL comments are not stored by the database server, and then get erased whenever you run `skeema pull`, `skeema format`,...

Makes sense, thanks! Converting this issue to a feature request -- I could see this being handled at the table / file granularity sometime. Column / single-line granularity would be...

My original intention was to leave this to other tools. But a number of folks have asked about this now, so I'm starting to reconsider :) The exact mechanics will...

Thanks, very open to community suggestions on this one! Hoping to gather as much input as possible, especially around different use-cases and workflows. Ideally let's all converge on a proposal...

Thanks @feihtthief, good suggestions! My own thinking around seed data has been moving in a similar direction lately. There are still some open questions, but I think this combination of...

Thanks @harveyramer, I agree this would be a useful feature. For the sake of transparency around user expectations though, I should clarify that this functionality is not yet under development,...