hi,
guess you have a table with more than 20k rows.
a select like "select * from your_table" blocks the hole table ;-(
pagination mode: off
read only: true
only when using the "pagination mode" dbforge does *not* block the table.
why is that ? is that a bug ?
i am now forced to work only in pagination mode to keep the table free for other processes.
thanks for any help!
mysql version: 5.5.8
dbforge: latest
select with large dataset blocks the whole table (bug?)
-
alexa
Hello,
When viewing table data in fetching mode (Paginal mode is turned off), dbForge Studio for Oracle doesn't receive all data at once, but gradually upon request (for instance: when scrolling data in the grid).
When using this mode, there is not closed cursor pending and, as a result, MyISAM tables are locked for editing unlike InnoDB tables.
In such situation Paginal mode should be used in order to view table data. You can specify in options to turn it on by default.
When viewing table data in fetching mode (Paginal mode is turned off), dbForge Studio for Oracle doesn't receive all data at once, but gradually upon request (for instance: when scrolling data in the grid).
When using this mode, there is not closed cursor pending and, as a result, MyISAM tables are locked for editing unlike InnoDB tables.
In such situation Paginal mode should be used in order to view table data. You can specify in options to turn it on by default.
thanks for your feedback, but i really don´t understand this behaviour.
why should it make sense to leave an open cursor at the db ?
mysql 5.5.8 in my case blocks the whole innodb-tabel and other requests
are waiting and get stuck ;-((
the big problem for me is: when not in paging mode i cannot really work while viewing the table data because other important processes are no longer able to work! ;-((
if i forget to close the table-view - because i go to toillet or out of the room - i block all tables i am viewing - i have never seen this bevor at any mysql client for windows.
i am really sorry, but i please you to think about this, becaue in fact, i cannot view safly data without using the pagination mode ;-(
thank you,
micha
ps.. i changed my email here in the forum because i didn´t get any emails, don´t know why... would be happy if you could send me a private message just for testing, thank you!
why should it make sense to leave an open cursor at the db ?
mysql 5.5.8 in my case blocks the whole innodb-tabel and other requests
are waiting and get stuck ;-((
the big problem for me is: when not in paging mode i cannot really work while viewing the table data because other important processes are no longer able to work! ;-((
if i forget to close the table-view - because i go to toillet or out of the room - i block all tables i am viewing - i have never seen this bevor at any mysql client for windows.
i am really sorry, but i please you to think about this, becaue in fact, i cannot view safly data without using the pagination mode ;-(
thank you,
micha
ps.. i changed my email here in the forum because i didn´t get any emails, don´t know why... would be happy if you could send me a private message just for testing, thank you!