106 words

Issue #125 - Issue with full cross joins

BugVersion: Priority: NormalStatus: FixedReplies: 1
#1
2012-01-16 11:29

hi,

There seems to be an issue with full cross joins & maps.

This query:

SELECT  $1
FROM com.lexware.vereinsverwaltung.verein.mitglied.Mitglied  $1
     LEFT JOIN $1.qubletFRAGMENTMAP $4,
     com.vereinsverwaltung.abrechnung.mitglied.MitgliedDebitorenKontoFragment $5
WHERE ($4=$5)

returns 30 entries from "Mitglied" whereas there should be 32 of them (see attached db). The two "Mitglied" entries with id 273 and 274 don't get selected eventhough they do have valid "MitgliedDebitorenKontoFragment" entity reference in their "qubletFRAGMENTMAP" map!?

quasado
quasado's picture
Joined on 2011-04-30
User Post #63
#2
2012-01-16 20:44

It seems that simple iteration on map values in JOIN has not been implemented and a map was handled as a collection of the first half of keys and values.

Thank you for this report. Build  2.3.5_06 fixes this issue.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
support
support's picture
Joined on 2010-05-03
User Post #854

Post Reply

Please read carefully the posting instructions - before posting to the ObjectDB website.

  • You may have to disable pop up blocking in order to use the toolbar (e.g. in Chrome).
  • Use ctrl + right click to open the browser context menu in the editing area (e.g. for using a browser spell checker).
  • To insert formatted lines (e.g. Java code, stack trace) - select a style in the toolbar and then insert the text in the new created block.
  • Avoid overflow of published source code examples by breaking long lines.
  • You may mark in paragraph code words (e.g. class names) with the code style (can be applied by ctrl + D).
  • Long stack traces (> 50 lines) and complex source examples (> 100 lines) should be posted as attachments.
Attachments:
Maximum file size: 32 MB
Cancel