[Lxr-dev] [ lxr-Bugs-2950793 ] genxref --reindexall with MySQL causes unknown table error

[SourceForge.net <no...@so...>]

Bugs item #2950793, was opened at 2010-02-12 20:55
Message generated for change (Comment added) made by ajlittoz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2950793&group_id=27350

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Database interface
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 5
Private: No
Submitted By: Patrick Gartung (gartung)
Assigned to: Andre-Littoz (ajlittoz)
Summary: genxref --reindexall with MySQL causes unknown table error

Initial Comment:
Running   genxref --reindexall   when using MySQL 4.x produces an unkonown table error from mysql server.

Using the syntax suggested at this site
http://www.portfolioofpb.com/blog/mysql-sql-error-unknown-table-in-MULTI+DELETE-solved

I modified lib/LXR/Index/Mysql.pm to use the correct syntax for mysql 4.x

----------------------------------------------------------------------

>Comment By: Andre-Littoz (ajlittoz)
Date: 2011-03-26 17:53

Message:
Closed with the agreement of submitter:
Was probably submitter against release 0.9.5 meanwhile Mysql.pm underwent
many changes among:
- no more aliases in SQL queries (which was causing the syntax error),
- change of 'release' now a reserved word in MySQL 5.x to 'releaseid'
- many small changes in sorting results
In release 0.9.8 Mysql.pm is deemed to be compatible with MySQL 4.x and
5.x

----------------------------------------------------------------------

Comment By: Andre-Littoz (ajlittoz)
Date: 2011-03-17 09:07

Message:
OK, I'll check to see if proposed change is "universal".
If not, since this part of LXR is rather object oriented, I'll create
another DB backend which could be selected through the 'dbname' config
parameter: using :mysql4: instead of plain :mysql:

----------------------------------------------------------------------

Comment By: Malcolm Box (mbox)
Date: 2011-03-14 21:43

Message:
Maintaining compatibility with MySQL 4.x is useful as there are plenty of
places still running this.

Does the proposed change work on 5.x - if so it seems it would be worth
keeping this in the main trunk.

----------------------------------------------------------------------

Comment By: Andre-Littoz (ajlittoz)
Date: 2011-03-13 09:32

Message:
MySQL 4.x ended 31 December 2010. Consequently is there still a need for
including this correction in the main line?

If somebody does need it, please resubmit and I'll create a (short lived)
branch in the CVS.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=2950793&group_id=27350