Joel Mukuthu

@blumamir thank you so much for sharing the info you did! It's great to know that this kind of thing is what the context is designed for. I'll look into...

@JamieDanielson thanks for the response. Just so I understand better, is it the "SQL Commenter" use-case that's unpopular or is there not enough justification to access attributes stored in the...

Yes that helps, thanks for responding and for all the work you and your team put in!

Thanks for responding! > Could you explain a bit more about why there’s a need for file name descriptions exceeding 200 characters? Yes of course. In my project, migration files...

> Can you work around this by changing the size of the field in the migrations history table? Cool, I can do that. Is there a particular reason why the...

Hi @JasonLuo-Redgate, what's the rationale for closing this issue?

Understood, and thanks for keeping it open!

Thanks for the suggestion, that does indeed work. However, I feel like it's too much burden to place on the user especially for this particular use-case. Ideally, I'd like to:...

> CREATE SCHEMA IF NOT EXISTS will fail if the user doesn’t have CREATE permissions (whether or not the schema exists) Indeed, I wasn't aware of that. I'm okay running...

Thanks for the pointers @benjie. Running the migrations ourselves solves this use-case. Closing.