I was already looking for a patch and found something similar at http://drupal.org/node/151910
I have applied the patch http://drupal.org/files/issues/151910_1.patch without any changes on the error message itself.
Therefore I assume, the patch is only for D6.

This is the warning:

user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'INNER JOIN _BDA_node_access na ON na.nid = node.nid WHERE (na.grant_view >= 1 AN' at line 1 query: INNER JOIN _BDA_node_access na ON na.nid = node.nid WHERE (na.grant_view >= 1 AND ((na.gid = 0 AND na.realm = 'all'))) LIMIT 0, 5 in /mnt/web8/41/10/5126210/htdocs/bda-de/includes/database.mysql.inc on line 174.

Any hints?

Comments

drumm’s picture

drumm
he/him
Location NY, US
commented
Version: 5.15 » 6.x-dev
Status: Active » Postponed (maintainer needs more info)

Is '_BDA_' your db table prefix set in settings.php? What node access modules are you using?

RaRi’s picture

RaRi commented
Version: 6.x-dev » 5.15

Hi drumm

this issue belongs to D5.15. I've seen the D6-dev in the issue track.

Ok .. not sure what you mean with node access module in detail .. anyway, these are the modules working with nodes:

// $Id: usernode.module,v 1.12.2.26 2008/06/10 11:39:54 fago Exp $
// $Id: node.module,v 1.776.2.33 2009/01/14 23:32:14 drumm Exp $
// $Id: system.module,v 1.440.2.46 2009/01/14 23:32:15 drumm Exp $
// $Id: nodefamily.module,v 1.19.2.16 2008/06/09 07:13:18 fago Exp $
// $Id: nodeprofile.module,v 1.7.2.35 2008/04/20 20:57:14 fago Exp $
// $Id: pageroute_nodefamily.module,v 1.2.2.11 2008/09/25 11:35:03 fago Exp $

and a couple of other modules .. if you need a complete list - more than this - just drop another message.

The prefix _BDA_ is set in the settings.php.
$db_prefix = '_BDA_';

RaRi’s picture

RaRi commented

Any news available?

RaRi’s picture

RaRi commented

Hello?? Somebody here?

dpearcefl’s picture

dpearcefl commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Considering the lack of activity on this issue and that Drupal v5 is no longer supported by for fixes or patches, I am going to close this ticket.