hi,
when i hit the arrow down button (accidentally) on a super large table, i can wait hours ;-(((
this preview should get a limit if the foreign table is too large.
if the other table has more than X records, you should trunc that result
and give a notice. this fetching-data window makes no sense otherwise.
i was forced to terminate the whole program because i cannot wait 30minutes to see the data ;-(
limit forgein table data view
Re: limit forgein table data view
We will investigate this issue and will answer you as soon as possible.
Re: limit forgein table data view
thanks....
Re: limit forgein table data view
Please check that you are using the latest version 8.0 https://www.devart.com/dbforge/mysql/st ... nload.html
Re: limit forgein table data view
of course i do ;-)
Re: limit forgein table data view
Hello,
Please send DDL of the tables you work with, and specify the number of records in the Parent table.
Best Regards.
Please send DDL of the tables you work with, and specify the number of records in the Parent table.
Best Regards.
Re: limit forgein table data view
hey alex,
is seems like, this bug is not very well reproducable.
it looks like, this only happens, when the connection got lost or something else.
so the window usually works as expacted. but sometimes, the loading screen gets stuck.
the only thing i can imagine is, that there is a problem with the connection or maybe
the "reconnect" does not work in that case, i don´t know. so it seems like, it hasn´t anything
todo with the tables itself, but with the connection. maybe your team can check, if the same
things apply with that window, as with the rest of the program. if i see this again, i don´t know
howto debug that, is there anything i can do/change/active ?
thanks
is seems like, this bug is not very well reproducable.
it looks like, this only happens, when the connection got lost or something else.
so the window usually works as expacted. but sometimes, the loading screen gets stuck.
the only thing i can imagine is, that there is a problem with the connection or maybe
the "reconnect" does not work in that case, i don´t know. so it seems like, it hasn´t anything
todo with the tables itself, but with the connection. maybe your team can check, if the same
things apply with that window, as with the rest of the program. if i see this again, i don´t know
howto debug that, is there anything i can do/change/active ?
thanks