sea-query
                                
                                 sea-query copied to clipboard
                                
                                    sea-query copied to clipboard
                            
                            
                            
                        add support for SQLite strict tables
this PR adds support for sqlite strict tables
it does so by adding a new variant to TableOpt variant
example:
create table test(a, b) (regular create statement)
create table test(a int, b int) strict (strict create statement)
Questions
- Is TableOptthe right place to put this functionality in?
- Does TableOpthave to be public given that there are builder methods for each individual option?
- I noticed that TableBuilder::table_prepare_create_statementhas only a default impl andTableOptsattempt to be rendered for any backend even though only MySQL (and SQLite starting with this PR) need those? I am pretty sure I understand why it is so (for the sake of code sharing probably) but wouldn't it make sense for each backend to have it's own implementation?
it might make sense to rewrite this PR in terms of TableModifier introduced in this PR
@evgeniy-terekhin hello! Sorry with the delay. I think is better split TableOpt into backend specific options, what do you think?