New answers tagged

1

Yes, that would block, and there is no way around that.


0

You can enumerate nested views through this query: SELECT DISTINCT sd.referenced_major_id, OBJECT_NAME(sd.referenced_major_id) as This_view, sd.object_id, OBJECT_NAME(sd.object_id) as need_this_view_to_work FROM sys.sql_dependencies sd WHERE EXISTS (SELECT 1 FROM sys.views v WHERE sd.object_id = v.object_id) AND EXISTS (SELECT 1 ...


0

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 to this CREATE SQL SECURITY INVOKER VIEW and test select the view from user.


0

where id <> 'ALL' is not sargable. Try to rewrite with id IN (...) or id > 'ALL' Create an index like this one : CREATE INDEX X ON precipitaion (id, "time") INCLUDE (country, prec)


0

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....


0

Before defining Stored Routines, etc, establish the desired CHARACTER SET and COLLATION. One way to do that is via SET NAMES. Also check 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.)


Top 50 recent answers are included