adding table twice results in unexpected behaviour in query

Bug #274867 reported by Rolf Leggewie
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenOffice
Invalid
Unknown
openoffice.org (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: openoffice.org

steps to reproduce problem:
* open http://www.openoffice.org/nonav/issues/showattachment.cgi/56852/OOo_debug.odb
* open "unnormalized table" query in edit mode
* Press F5, the query runs fine and displays three rows
* return to edit mode
* press F7 and add the products table for a second time
* press F5 to run the query again and see that there are a number of erroneous rows in the result

still present even in m31

The SQL statement that returns the correct results is

SELECT "products"."productName", "categories"."categoryName" FROM "products", "categories" WHERE "products"."categoryID" = "categories"."categoryID"

the one after adding the table for the second time is

SELECT "products"."productName", "categories"."categoryName" FROM "products", "categories", "products" AS "products_1" WHERE "products"."categoryID" = "categories"."categoryID"

Revision history for this message
Chris Cheney (ccheney) wrote :

Do you still have this problem with openoffice.org 1:2.4.1-9ubuntu2 in Ubuntu 8.10?

You didn't mention which version of openoffice.org, version of ubuntu or platform you are using.

Please file bugs using Help->Report a bug in the future.

Thanks,

Chris

Changed in openoffice.org:
status: New → Incomplete
Revision history for this message
Rolf Leggewie (r0lf) wrote :

m31 is the codeword for a development release of OOo3. So this problem is present even past post-Intrepid, post-2.x releases. Ubuntu hardy is my base testing line.

Changed in openoffice.org:
status: Incomplete → New
Revision history for this message
Chris Cheney (ccheney) wrote :

Which bug report upstream is that file in the url from?

Changed in openoffice.org:
status: New → Incomplete
Revision history for this message
Rolf Leggewie (r0lf) wrote :

It is from an unrelated (even invalid) issue I reported upstream. The number is 94343.

May I kindly ask to keep the "New - Incomplete - New" ping-pong down to a minimum? I will try to respond to your questions in a timely manner. All these questions and settings bugs to "Incomplete" is nice, but it doesn't always bring resolution even one step closer. I have given all necessary steps to reproduce this bug. Feel free to reproduce or let us know if it works for you. That'll get us moving. Thank you for your attention.

Changed in openoffice.org:
status: Incomplete → New
Chris Cheney (ccheney)
Changed in openoffice.org:
status: New → Triaged
Revision history for this message
Chris Cheney (ccheney) wrote :

Can you report this bug upstream directly since you verified it doesn't work for you even with the official 3.0.0?

Thanks,

Chris Cheney

Chris Cheney (ccheney)
Changed in openoffice.org:
status: Triaged → Incomplete
Revision history for this message
Rolf Leggewie (r0lf) wrote :

The incomplete status can be a pest at times - sigh.

What is incomplete about this report? I can only see the misguided effort to get this valid and complete report off the radar. That's not helping to create a better Ubuntu!

Whether or not this issue has or has not been reported upstream has absolutely nothing to do with Ubuntu. If you don't believe me, pause for a second and think about why Launchpad has this great facility to track upstream and Ubuntu status separately.

Let's try to track and fix issues instead of blindly closing the greatest number of open tickets.

Changed in openoffice.org:
status: Incomplete → Triaged
Changed in openoffice:
status: Unknown → Confirmed
Revision history for this message
Rolf Leggewie (r0lf) wrote :
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Firefox downloads the file as read-only. When opening the sample file like that, ooffice will throw a rather cryptic and unhelpful error message (something Java-related), so don't forget to mark the file as read-write before opening.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

This is actually working as designed (although I would have assumed that adding a table without adding a field from it would not change the resultset)

setting to invalid.

Changed in openoffice.org:
status: Triaged → Invalid
Changed in openoffice:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.