Creating new views in dbForge 2020 - code formatting?
Posted: Tue 15 Jun 2021 03:13
Hi, this post is similar to another question I've posted here on the forums, but this refers specifically to table views (rather than stored procedures or functions).
When I create a view with a simple SELECT * (all) statement, the view gets created with FULL table column names with database name included for each column and am wondering if this behavior of dbForge or MySQL. The problem is I want the view definition to be DYNAMIC. Because the generic SELECT * statement is replaced, when a schema change is made to the target table the view cannot be accessed due to an error caused by schema mismatch. How can I disable this view rewrite on save? Please help. Again...this is FRUSTRATING. Otherwise and notwithstanding, I absolutely LOVE dbForge. For me, there is no suitable substitute.
Thank you.
When I create a view with a simple SELECT * (all) statement, the view gets created with FULL table column names with database name included for each column and am wondering if this behavior of dbForge or MySQL. The problem is I want the view definition to be DYNAMIC. Because the generic SELECT * statement is replaced, when a schema change is made to the target table the view cannot be accessed due to an error caused by schema mismatch. How can I disable this view rewrite on save? Please help. Again...this is FRUSTRATING. Otherwise and notwithstanding, I absolutely LOVE dbForge. For me, there is no suitable substitute.
Thank you.