Bug 34394

As I can understand: in Calc we first select and/or and only then Field Name
and in Base in reverse order: first Field name and then and/or.
And should be available in both orders in Calc and in Base.

> As I can understand: in Calc we first select and/or and only then Field
> Name and in Base in reverse order

@sasha:
Yes, that's my observation. Do you agree with my impression, that that difference is unexpected, or can you find a good reason for that different handling, so that it might be intended?

Alas, I can not. I almost never use LibreBase because FirebirdSQL is unavailable in Base. And all my data is in Firebird database. So I have almost no experience using Base. My be in future Base will be more useful and I can use it with real world data. Then I can say what it better on practice.

(In reply to comment #3)
> Alas, I can not. I almost never use LibreBase because FirebirdSQL is
> unavailable in Base. And all my data is in Firebird database. So I have almost
> no experience using Base. My be in future Base will be more useful and I can
> use it with real world data. Then I can say what it better on practice.

Hi Sasha,

FYI, how to connect to firebird from OOo here :
http://www.ibphoenix.fr/spip.php?article24

The same should also be applicable for LibO.

Alex

PS: Sorry for hijacking the thread.

I can confirm this, although it seems to me (from memory) that this behaviour has been present for years. 

Alex

change status to confirmed. It would be a useful enhancement.

(In reply to comment #4)
> (In reply to comment #3)
> > Alas, I can not. I almost never use LibreBase because FirebirdSQL is
> > unavailable in Base. And all my data is in Firebird database. So I have almost
> > no experience using Base. My be in future Base will be more useful and I can
> > use it with real world data. Then I can say what it better on practice.
> 
> Hi Sasha,
> 
> FYI, how to connect to firebird from OOo here :
> http://www.ibphoenix.fr/spip.php?article24
> 
> The same should also be applicable for LibO.
> 
> Alex
> 
> PS: Sorry for hijacking the thread.

Also look up on Google or your favorite search engine :

OOoFBvp.pdf (be careful, lots of links that you can find lead nowhere and one even took me to a Spanish adult content site)

http://www.oooforum.org/forum/viewtopic.phtml?t=337

Alex

(In reply to comment #7)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > Alas, I can not. I almost never use LibreBase because FirebirdSQL is
> > > unavailable in Base. And all my data is in Firebird database. So I have almost
> > > no experience using Base. My be in future Base will be more useful and I can
> > > use it with real world data. Then I can say what it better on practice.
> > 
> > Hi Sasha,
> > 
> > FYI, how to connect to firebird from OOo here :
> > http://www.ibphoenix.fr/spip.php?article24
> > 
> > The same should also be applicable for LibO.
> > 
> > Alex
> > 
> > PS: Sorry for hijacking the thread.
> 
> Also look up on Google or your favorite search engine :
> 
> OOoFBvp.pdf (be careful, lots of links that you can find lead nowhere and one
> even took me to a Spanish adult content site)
> 
> http://www.oooforum.org/forum/viewtopic.phtml?t=337
> 
> Alex


And this :

http://www.oooforum.org/forum/viewtopic.phtml?t=61507&highlight=firebird


Alex

On Windows and Linux 32 bit using ODBC Firebird works OK.
But ODBC has restrictions on SQL language. It means that I can not copy-paste SQL statments from another program to LibreBase. I need write my own requests that they can work in Base.
On Linux 64 bit is Bug 34432 - firebird ODBC not work
It looks that it is not our bug. Problem somewhere in ODBC driver. And if LibO would have ability of direct connection to FirebirdSQL, no unnecessary dependency of such bugs would be.
Thanks for interesting in my problem

On a Debian Wheezy x86-32, with a git version from Master repository, I made these tests :
- in Base, I opened the Address database and added 2 lines. Then I tried Standard filter and first condition is disabled. But as soon as you select the Field Name, the "Condition" and "Value" are enabled and you can choose your condition and value.
- same test on Writer with F4 and bibliography database, same results.

I tested too on a Win7 (since it's the environment indicated on this report) with LibreOffice 3.4.3 OOO340m1 (Build:302), I did the same 2 tests and I got the same results.


Have you still got this problem or did I missed something and did something wrong ?

Created attachment 51872 [details]
Screenshots Comparing Filter View in Database and Calc

@Julien Nabet:
There is no problem, but an inconsistence. Your description seems to show the same observations as I did.

The observations can be reproduced easily with an arbitrary calc sheet and biblio database.

[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html

remains in LibO 3.5.0 beta 1
in database button and/or available only after selecting field name
(expected that user can select button and/or and only then select field names, as in Calc)

Please read this message in its entirety before responding.

Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed.

If you have time please do the following:
1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer).
2) If it is present please leave a comment telling us what version of LibreOffice and your operating system.
3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System

Please DO NOT
1) Update the version field
2) Reply via email (please reply directly on the bug tracker)
3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 
LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link:
https://wiki.documentfoundation.org/QA/BugTriage

There are also other ways to get involved including with marketing, UX, documentation, and of course developing -  http://www.libreoffice.org/get-help/mailing-lists/. 

Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material

Adding self to CC if not already on