Devart Forums

thanks!!!

nice! thanks for letting us know !!

i assume the answer is no.

https://stackoverflow.com/a/4519946

yes, the context-menu should have a new item like "Compare Schema" and - why not - "Compare Data", so when you havce selected two tables and the compare-wizard opens, you don´t have to chosse the mysql connection, database and tables, because you already did before.

hi,
when choosing two tables it would be nice to compare both directly from the context menu:



this would save so much time instead of going through the whole compare wizard ;)

thanks,
micha

hi,

of course, using PHP as a proxy is the worst type of connection you can choose ;)
every request goes to the webserver, the webserver talks to the PHP-daemon, and the
PHP process finally talks to MySQL and everything has to go back the same way, bad, very bad ;)

the PHP tunnel is something you should use when there is no other option left.
the best option, of course, is a direct connection, without anything between.
but because of safety, MySQL never should be open to the outside world.
so the logical solution is, to connect via SSH directly to your server and from there to 127.0.0.1 to your MySQL, this connection is as fast as using a direct connection, you won´t notice any difference ;)

cheers,
micha

i was now forced to go back to 9.0.791 !!

PLEASE FIX THIS !!!
THX!

the problem also exists with version: 9.0.890 !

hi there,

the latest version of dbforge enterprise 9.0.897 has 2 SUPER ANNOYING problems
that make is nearly impossible to work with. i thought to see an update soon because
I know the problem is not related to me - my colleague who recently updated to the
latest version now has the same problems - and it´s a BIG ONE - so I really expect a hotfix here as soon as possible!

problem 1:

if you press CTRL+N to create a new tab, dbforge doesn´t open only one tab, it opens endlessly new tabs!!!
the only way to stop this is to press ESC. so if you don´t hit ESC directly after CTRL+N you will end up with 20 new tabs,
this is horrible !!!!

see: https://www.youtube.com/watch?v=RCgtoDjS8C0

problem 2:

even worse: but not 100% reproducible. if you paste something in (CTRL+V) dbforge does it twice or forever, unless
you press ESC. again, this makes working with that software nearly impossible, because like with the tabs,
you are now forced to press ESC immediately after your regular HOTKEY. so now it´s:

CTRL+N (press ESC super fast after that to stop creating any more tabs)
CTRL+V (press ESC super fast after that to stop any further postings)

again: these problems are NOT related to my PC or my keyboard!
a colleague of mine was working with an older version and never experienced these problems.
he recently updated and told me, that he now has the same problems!

we a trying to downgrade till this is fixed because it´s pure horror working like that !

PLEASE FIX THAT AS SOON AS POSSIBLE !!

thanks!
micha

hi dzhanhira,

thanks, setting that value to 1 seems to work.
good to know !!

thanks,
micha

hi,

is MariaDB-1:10.7.4 official supported?
because dbforge does
but server says: because there is not table, it´s a view and it´s called "user" (small >u<)

thanks,
micha

okay, in that case, i do understand.
anyway: strange that mariadb has a problem with something that is inside "order by" but does not point to the column used in "order by" instead to something that is used in "SELECT...." on top....

¯\_(ツ)_/¯

with "coordinates" you mean line number and position in that line ?

hi,

your massage makes no sense at all, sorry.
OF COURSE dbforge gets the information from the server which column makes oroboems, but the question is "where" to highlight the column if the column is used several times inside a query (and u know that).

so when the server says that a unknown column was used inside the "order by" - it would make much more sense to highlight that column that was used in the "order by" and not anywhere else. (and you know that).

so you know exactly what I am trying to explain here. but it's not a big deal and if u want to ignore that unsightliness, okay - I just wanted to help you making things better.

cheers

in another example dbforge marks the field correctly:



:-)