SELECT INTO problem

Note: please leave bug reports and feature requests on

SELECT INTO problem

Postby asakz » Fri Sep 14, 2012 2:17 pm

Hi,

when using "SELECT * INTO backupTable FROM orginalTable" statement to backup table, only first 200 rows are inserted into the backup table. Evidently, DBeaver appends to SELECTs limiting condition to not flood the grid with large amount of data. I know that this limit can be set in the Preferences dialog, but in case of SELECT INTO clause, I think that such behavior is undesirable...

Thanks.
asakz
 
Posts: 2
Joined: Fri Sep 14, 2012 2:02 pm

Re: SELECT INTO problem

Postby Serge » Fri Sep 14, 2012 4:20 pm

Hello,

I assume you use MySQL.
Indeed, DBeaver uses LIMIT clause to limit query results and is affects on SELECT INTO statement. It is definitely a bug and it will be fixed in the next version.

Thanks for report!
Serge
 
Posts: 1526
Joined: Sat Feb 26, 2011 8:24 pm
Location: SPb

Re: SELECT INTO problem

Postby asakz » Tue Sep 18, 2012 8:04 am

asakz
 
Posts: 2
Joined: Fri Sep 14, 2012 2:02 pm

Re: SELECT INTO problem

Postby Serge » Tue Sep 18, 2012 8:47 am

Hi,

:( Actually it is very driver-dependent problem. At the moment MySQL is the only database where we modify queries to limit row count, all other drivers executes user quries "as is" without any additions.
JDBC API allows to limit resultset size but it should affect only directly returned resultsets not any INSERT/UPDATE statements.
I think you use jTDS driver which works incorrectly with this function (there is an official bug: ). Right now I'd suggest you to use native Microsoft driver to avoid this problem.
We'll try to make some workaround in the next version.

Thanks!
Serge
 
Posts: 1526
Joined: Sat Feb 26, 2011 8:24 pm
Location: SPb


Return to Support



Who is online

Users browsing this forum: Google [Bot] and 4 guests