quick filter on datetime problem

[fallingdown]

I have noticed that since daylight savings time went into effect, when I use the quick filter (right click -> order/filter) on a date column in a result set the applied datetime filter is one hour later than what I wanted. I can manually change it. I just not sure if that is a bug or a problem with some configuration or something.

Thanks!

DBeaver 2.1.0
Windows 7
Oracle 11g

[Serge]

Hi,

DBeaver executes filtered queries in a plain form - you may find these queries in Query Manager view and try to execute them manually. Thus you will see that there is no magic in result set filtering
I believe that the problem is on database side (maybe server time differs from client or something like that). in any case DBeaver doesn't modify filter parameters anyhow, they are passed to database as is.

If you will find any solution of this problem - please post it here.

Thanks

[fallingdown]

Well, that could be it, but based on the following I am not entirely convinced it is server time related as the server is in the same building as me (although I will investigate the time element).

I opened a table to browse the data.
Right-clicked on a record on the date column, for this example call it row_eff_datetime. The value in the data browser that I see for this example is 2013-04-09 14:39:38 (using yyyy-MM-dd HH:mm:ss format)
Navigated to the Order/Filter options.
I see a list of quick filter options, the first few are listed as:
row_eff_datetime = 2013-04-09 14:39:38
row_eff_datetime <> 2013-04-09 14:39:38
row_eff_datetime > 2013-04-09 14:39:38
row_eff_datetime < 2013-04-09 14:39:38

I select the second option (<>).
Now I open the Query Manager view.
The most recent query shows as follows
SELECT * FROM MYSCHEMA.MY_TABLE WHERE ROW_EFF_DATETIME <> TO_DATE('2013-04-09 15:39:38','YYYY-MM-DD HH24:MI:SS')

Everything up to this last point would lead me to believe that my query would be predicated on 2013-04-09 14:39:38, but the actual query is filtered for one hour later.

[fallingdown]

I checked the clock on the server on the OS and the current time from the database (select sysdate, current_date, current_timestamp from dual;). All show the correct time.

I am getting the same behavior on a totally separate server as well.

I tested it on DBeaver 2.1.0 on a Windows 7 machine and DBeaver 2.0.6 on Linux. Same thing.

Hmmm. I wonder if it's related to the oracle jdbc driver?

[Serge]

I've just reproduced it.
It seems that datetime conversion occurs somewhere after result set fetch and filter parameters binding.
Unfortunatelly right now (and during next 10 days) I'm in a business trip and can't access my dev environment. But this issue is definitely a problem which should be solved. So I'm going to fix it in the next version (planned to be released till the end of April).

Thanks for detailed report!

[fallingdown]

Cool Thanks!