blocked in work because of selecting information_schema
Posted: Thu 18 Jun 2020 19:12
hi alex,
i fully understand, that dbforge wants to select "information_schema" for the schema.
my big problem is: i have some very large tables, that get re-created every X minutes. this sometimes
takes more than 20minutes. so i got stuck more than 1 or 2 minutes when dbforge is trying to fetch the information_schema in exact that moment. this is super annoying ;-((
maybe there is a way - a switch or something - that dbforge fetches the information_schema without getting blocked,
like read uncommitted or something like that.
getting blocked several times the day makes working no fun ;(
so maybe there is an option to do more caching of the schema or fetching schema without getting blocked.
in case the user realizes, that something is missing, there could be a hotkey to fetch schema the regular way,
like now.
thanks,
micha
i fully understand, that dbforge wants to select "information_schema" for the schema.
my big problem is: i have some very large tables, that get re-created every X minutes. this sometimes
takes more than 20minutes. so i got stuck more than 1 or 2 minutes when dbforge is trying to fetch the information_schema in exact that moment. this is super annoying ;-((
maybe there is a way - a switch or something - that dbforge fetches the information_schema without getting blocked,
like read uncommitted or something like that.
getting blocked several times the day makes working no fun ;(
so maybe there is an option to do more caching of the schema or fetching schema without getting blocked.
in case the user realizes, that something is missing, there could be a hotkey to fetch schema the regular way,
like now.
thanks,
micha