Hi,
i recognize a change in the sql statement
in oxattributlist::loadAttributes that brake somethings.
Old(4.6.4) = $sSelect = "select {$sAttrViewName}.*, o2a.* from
{$sViewName} as o2a ";
New = $sSelect = "select {$sAttrViewName}.`oxid`,
{$sAttrViewName}.`oxtitle`, o2a.`oxvalue` from {$sViewName} as o2a ";
Ok, we load less data. Nice BUT now i got a problem.
The oxid for the object isnt anymore the oxid of the oxobject2attribute
entry, its the id of the oxattribute that brings me to oxlist::assignArray
that has this lines :
if ( $oListObject->getId() ) {
$this->_aArray[ $oListObject->getId() ] = $oListObject;
} else {
$this->_aArray[] = $oListObject;
}
So, in case we got for a article a multi assignment of an attribute(I know
thats not possible with the standard OXID backend), for example you got a
product and an attribute Disigner and you want assign to this product more
than one Designer (comma seperated in one assignment is no option) you will
now only get one back. The assignArray function will override the multi
assignments!
I can fix it for my purpose but i want to ask you if you think this is more
a bug as a feature.
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
