Closed (outdated)
Project:
Bibliography Module
Version:
6.x-1.1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Apr 2009 at 18:07 UTC
Updated:
20 Dec 2018 at 17:14 UTC
Jump to comment: Most recent
Comments
Comment #1
rjerome commentedYour supposed to be on vacation!! Stop looking at this ;-)
I did put those distincts back although slightly differently in that it's now DISTINCT(n.nid), n.*, biblio.* bla bla bla... I would have thought that would have the same effect, but perhaps I was wrong.
Ron.
Comment #2
Frank Steiner commentedOk ok ;-) Actually I would also think that the nid should be unique enough... I can test this here next week.
Comment #3
Frank Steiner commentedOk, I couldn't resist to use my ssh account to check this, sorry ;-) It's in biblio_export where I added a "GROUP BY n.nid" (because I wasn't able to use a DISTINCT correctly, always got an empty result):
$query = db_rewrite_sql("SELECT * FROM {node} n left join {biblio} b on n.vid=b.vid WHERE n.nid=%d GROUP BY n.nid");Then it works. Reason is like before the node_access stuff due to the node_privacy_by_role module.
cu,
Frank
Comment #4
rjerome commentedYour as bad as I am!! You just can't leave this stuff alone.
It should only get to that line if there is no SESSION information available, which goes back to our previous discussion I guess. What if you put a DISTINCT (n.nid), n.* FROM ... on that line.
Ron.
Comment #5
Frank Steiner commentedDISTINCT (n.nid), n.*, b.* FROM... works, otherwise parts from the biblio table are missing.
Is there a (performance) difference between DISTINCT and GROUP? Or are they just syntactic sugar?
Comment #6
rjerome commentedI don't claim to be an SQL guru, but from what I've read it seems the latter is true, for most cases they are more or less the same.
Ron.
Comment #7
liam morlandThis version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.