You can enumerate nested views through this query:
OBJECT_NAME(sd.referenced_major_id) as This_view,
OBJECT_NAME(sd.object_id) as need_this_view_to_work
EXISTS (SELECT 1 FROM sys.views v WHERE sd.object_id = v.object_id)
AND EXISTS (SELECT 1 ...
i got same issue
on my case, my resolution re-create the view with change this part from
CREATE ALGORITHM=UNDEFINED DEFINER=`sst_user`@`10.148.0.0/255.255.240.0` SQL SECURITY DEFINER
CREATE SQL SECURITY INVOKER VIEW
and test select the view from user.
Okay, if I'm reading your requirements correctly, this should work (or can be made to work without too much effort). If it isn't already, the primary key should be entity_id + the date column, or at least a UNIQUE constraint added for those two columns. For optimal performance, the tables should be index-organized on entity_id + the appropriate date column....
Before defining Stored Routines, etc, establish the desired CHARACTER SET and COLLATION. One way to do that is via SET NAMES.
SHOW CREATE DATABASE
utf8mb4_unicode_520_ci is newer than utf8mb4_unicode_ci. (I don't know what collation changes were made by Unicode between their 4.0.0 and 5.2.0 versions. You may never notice a difference.)