lxr-developer — Don't use, active developers only

[Lxr-dev] [ lxr-Bugs-1807357 ] MySQL server has gone away at lib/LXR/Index/Mysql.pm line258

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

Bugs item #1807357, was opened at 2007-10-04 09:08
Message generated for change (Settings changed) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1807357&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: genxref
Group: v0.9.5
>Status: Closed
>Resolution: Rejected
Priority: 5
Private: No
Submitted By: aarunendra (aarunendra)
Assigned to: Nobody/Anonymous (nobody)
Summary: MySQL server has gone away at lib/LXR/Index/Mysql.pm line258

Initial Comment:
I am indexing the Biweekly releases. When I ran the genxref on the smaller releases (Size of the release is less) everything is going fine. For larger releases (more in size) initially for couple of release it worked fine. After that following error is coming while running genxref

------------------------------------------------------
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 201.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 201.
BTYPE was: atom
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 204.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 204.
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 204.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 204.
BTYPE was: atom
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 206.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 206.
BTYPE was: atom
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 208.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 208.
BTYPE was: atom

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

Identifier search is not working 

Can some one help how to overcome the above problem.

Thanks


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

>Comment By: Malcolm Box (mbox)
Date: 2009-03-23 12:34

Message:
Not a defect in LXR - the Mysql server has crashed.

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

Comment By: Malcolm Box (mbox)
Date: 2007-10-04 21:45

Message:
Logged In: YES 
user_id=215386
Originator: NO

Looks like your MySQL server has crashed, or the DBI driver to it has lost
the connection.

I suggest checking your mysql logs to see what's happening.


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

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

[Lxr-dev] [ lxr-Bugs-1716172 ] small typo in INSTALL

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

Bugs item #1716172, was opened at 2007-05-09 23:19
Message generated for change (Comment added) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1716172&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: Documentation
Group: current cvs
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Malcolm Box (mbox)
Summary: small typo in INSTALL

Initial Comment:
>From the CVS version of INSTALL,

I think line 112:
  112  'ectagsconf' => \
       '/usr/lib/perl5/site_perl/Lang/ectags.conf',

should read:
  112  'ectagsconf' => \
       '/usr/lib/perl5/site_perl/LXR/Lang/ectags.conf',


missing 'LXR'

--
tehmasp

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

Comment By: Malcolm Box (mbox)
Date: 2009-03-23 12:32

Message:
This has now been fixed in CVS.

If you can install the new version and check that it solves your
problem, then it would be very useful.

Thanks for reporting this defect and helping to make LXR better.

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

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

[Lxr-dev] [ lxr-Bugs-1209273 ] "release" a reserved word in MySQL 5.x

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

Bugs item #1209273, was opened at 2005-05-26 17:33
Message generated for change (Comment added) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&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: Fixed
Priority: 5
Private: No
Submitted By: Jeff Warnica (jeffwarnica)
Assigned to: Malcolm Box (mbox)
Summary: "release" a reserved word in MySQL 5.x

Initial Comment:
And perhaps earlier versions too.

The table lxr_releases can not be created..

The MySQL docs claim that you can use reserved words as
identifiers if you quote them, but testing the CREATE
TABLE with "release" quoted also failed. 

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

Comment By: Malcolm Box (mbox)
Date: 2009-03-23 12:27

Message:
This has now been fixed in CVS.

If you can install the new version and check that it solves your
problem, then it would be very useful.

Thanks for reporting this defect and helping to make LXR better.

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

Comment By: Joshua Barr (stemcel)
Date: 2007-07-26 23:04

Message:
Logged In: YES 
user_id=1838421
Originator: NO

Summary says that CREATE TABLE with "release" quoted fails, but you need
to use back ticks (i.e. `release`) to quote the keyword. All instances of
"release" in initdb-mysql and all those that are not Perl scalars in
..../lib/LXR/Index/MySQL.pm need to be quoted or have their names changed.
"release" is not a reserved keyword in MySQL 4.x.

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

Comment By: aaron (ipo23)
Date: 2007-05-13 01:44

Message:
Logged In: YES 
user_id=1619342
Originator: NO

same here - aaron@texas:/usr/share/doc/lxr-cvs/examples$ mysql --version
mysql  Ver 14.12 Distrib 5.0.38, for pc-linux-gnu (x86_64) using readline
5.2
aaron@texas:/usr/share/doc/lxr-cvs/examples$ 

release needs to be quoted with backquotes as a field definition as well
as in the primary key clause
then it works

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

Comment By: Brian St. Pierre (bstpierre)
Date: 2006-10-06 18:40

Message:
Logged In: YES 
user_id=10357

Looking in CVS, it doesn't appear that the patch was applied to Mysql.pm.
(I do see the change in initdb-mysql.)

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

Comment By: Danny (perunaion)
Date: 2006-09-16 03:20

Message:
Logged In: YES 
user_id=1047608

Release 1559658, attempts to address this issue.
Its a patch of the two modified files (Mysql.pm and
initdb-mysql).  Hopefully that will help fix this.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2006-07-14 00:59

Message:
Logged In: NO 

You need to change BOTH the initdb-mysql script and the
Mysql.pm module (8 occurrences total).  You can either
change the name of the 'release' field (which was the route
I took), or quote it with back-ticks.

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

Comment By: Laurence Passmore (lmop)
Date: 2006-06-07 09:25

Message:
Logged In: YES 
user_id=1410237

I think you need to change lib/LXR/Index/Mysql.pm thus:

1) s/r.release/r.`release`/g

2) s/release =/`release` =/g

3) s/ release\)/ `release`\)/g

(I say think because I haven't tested it; I currently have other issues
with my LXR 
installation that is preventing me from getting it working at all...)

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

Comment By: Malcolm Box (mbox)
Date: 2006-06-06 23:24

Message:
Logged In: YES 
user_id=215386

Apparently not a good fix - reopening

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

Comment By: Malcolm Box (mbox)
Date: 2006-06-05 11:16

Message:
Logged In: YES 
user_id=215386

Now fixed in CVS. Thanks to lmop for the fix.

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

Comment By: S Melody (prplehaze2)
Date: 2006-05-31 16:37

Message:
Logged In: YES 
user_id=911986

I used this fix to create the tables, but indexing seems to
fail, most likely because release is a reserved word:

DBD::mysql::st execute failed: 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 'release =
'head'' at line 1 at lib/LXR/Index/Mysql.pm line 209.
DBD::mysql::st execute failed: 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 'release)
values ('387', 'head')' at line 1 at lib/LXR/Index/Mysql.pm
line 213.


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

Comment By: Laurence Passmore (lmop)
Date: 2005-12-21 17:20

Message:
Logged In: YES 
user_id=1410237

This is a simple fix. initdb-mysql should be changed as follows
(basically, 
backtick (`) the column name `release` to escape/quote it):

create table lxr_releases (
        fileid          int not null references lxr_files,
        `release`       char(255) binary not null,
        primary key     (fileid, `release`)
);

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

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

[Lxr-dev] [ lxr-Feature Requests-1898059 ] cursor in the input box

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

Feature Requests item #1898059, was opened at 2008-02-20 17:38
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=1898059&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: Browsing Interface
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: cursor in the input box

Initial Comment:
Hi,

First of all, thank you for the great work.
I am not sure if this has been discussed before but if not, I would like to ask if you can make a small change to put the cursor in search input box by default so that I don't have to move my mouse to go to input box to type the keyword to search.

In fact, google also does this so I found it very conveneint to type the keyword as soon as I get there.

Thank you.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2009-03-13 13:15

Message:
e8llju 16430490 3017ym [URL=http://refruit.com/rsstmp/mietwagen/] mietwagen
[/URL] <a href="http://refruit.com/rsstmp/mietwagen/"> mietwagen </a>
http://refruit.com/rsstmp/mietwagen/ 

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

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

[Lxr-dev] [ lxr-Feature Requests-1898059 ] cursor in the input box

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

Feature Requests item #1898059, was opened at 2008-02-20 09:38
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=1898059&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: Browsing Interface
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: cursor in the input box

Initial Comment:
Hi,

First of all, thank you for the great work.
I am not sure if this has been discussed before but if not, I would like to ask if you can make a small change to put the cursor in search input box by default so that I don't have to move my mouse to go to input box to type the keyword to search.

In fact, google also does this so I found it very conveneint to type the keyword as soon as I get there.

Thank you.

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

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

[Lxr-dev] [ lxr-Patches-1852726 ] add javascript syntax

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

Patches item #1852726, was opened at 2007-12-18 00:27
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390119&aid=1852726&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: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: arno. (arno-)
Assigned to: Nobody/Anonymous (nobody)
Summary: add javascript syntax

Initial Comment:
Hi,
here is support for javascript syntax. I've used it for a few weeks, and it looks quite ok.

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

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

Re: [Lxr-dev] Updates?

[Arne G. G. <ar...@gl...>]

Maximilian Wilhelm wrote:
> http://lxr.linux.no seems to be updated now :)

So it is.  Seems to be running fairly ok, although there are a few
performance hotspots that could do with a bit of attention.

> Looks nice. Kinda 'web 2.0' ;-)

Thanks.  Yeah, kinda. :)

> Has the diff feature gone or did I just miss it?

It's gone for the time being.  I had planned to implement it before
switching lxr.linux.no, but decided it had been held up for too long.
I'm planning to reimplement the diff feature alongside a history
feature, where you could open a drop down box of the last 10-15 viewed
files and either jump back to them or compare them to the currently open
file.  (As the old implementation of the diff feature depended on the
version and arch variables, the number of available dimensions you could
show differences in were halved when the "arch"-variable (or rather, the
"arbitrary user-specified path variables") feature was removed.)

-- 
								Arne.

Re: [Lxr-dev] Updates?

[Maximilian W. <ma...@rf...>]

Am Thursday, den 29 November hub Arne Georg Gleditsch folgendes in die Tasten:

> Arne Georg Gleditsch wrote:
> > For sure.  lxr.linux.no is due to move to new, dedicated hw in the near
> > future, and I was hoping to put up a beta version with source and the
> > like on that one.  I was hoping to have this done by now, actually.  If
> > it looks to take much more time, I'll put the source up somewhere else
> > in the meantime.

> Famous last words...  For real this time, lxr.linux.no is due to move to
> new hardware and experimental code pretty soon.  For those of you who'd
> like to have a look at what that looks like, lxr-test.linpro.no is
> operational with what's going to be the new site.  (The path to the git
> repo on the main page needs adjustment until dns is updated.)

http://lxr.linux.no seems to be updated now :)

Looks nice. Kinda 'web 2.0' ;-)

Has the diff feature gone or did I just miss it?

Ciao
Max
-- 
	Follow the white penguin.

Re: [Lxr-dev] Updates?

[Arne G. G. <ar...@gl...>]

Arne Georg Gleditsch wrote:
> For sure.  lxr.linux.no is due to move to new, dedicated hw in the near
> future, and I was hoping to put up a beta version with source and the
> like on that one.  I was hoping to have this done by now, actually.  If
> it looks to take much more time, I'll put the source up somewhere else
> in the meantime.

Famous last words...  For real this time, lxr.linux.no is due to move to
new hardware and experimental code pretty soon.  For those of you who'd
like to have a look at what that looks like, lxr-test.linpro.no is
operational with what's going to be the new site.  (The path to the git
repo on the main page needs adjustment until dns is updated.)

-- 
								Arne.

[Lxr-dev] [ lxr-Feature Requests-942911 ] Subversion Support

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

Feature Requests item #942911, was opened at 2004-04-27 03:23
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390120&aid=942911&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: General
Group: Next Release
Status: Open
Priority: 5
Private: No
Submitted By: teewurstmann (teewurstmann)
Assigned to: Nobody/Anonymous (nobody)
Summary: Subversion Support

Initial Comment:
It would be nice to integrate support for Subversion
into a future release of LXR. Since LXR already
supports CVS support for Subversion shouldn't be too
hard to implement.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2007-11-27 03:19

Message:
Logged In: NO 

is it comming or not?
would be very nice to hear about...

think this is a good feature

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

Comment By: Matt England (mengland)
Date: 2006-12-24 05:48

Message:
Logged In: YES 
user_id=10503
Originator: NO

Is any Subversion-support activity underway?

If not, can anyone provide some pointers on how to make an appropriate
lib/LXR/Files/SVN.pm and anything else that's needed to make LXR parse a
Subversion repository?

-Matt

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

Comment By: Vaish (vaish)
Date: 2006-04-24 08:19

Message:
Logged In: YES 
user_id=1508835

Is there any workaround for LXR to access subversion repository?

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

Comment By: Roland Schwingel (rolandschwingel)
Date: 2004-10-20 01:58

Message:
Logged In: YES 
user_id=710704

Oh yes!!

This would be really cool to have... I am at present
searching for an application doing this...

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

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

[Lxr-dev] [ lxr-Patches-1832713 ] Implement case-insensitive language processing

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

Patches item #1832713, was opened at 2007-11-15 19:43
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390119&aid=1832713&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: Browsing
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Craig (mr_wednesday)
Assigned to: Nobody/Anonymous (nobody)
Summary: Implement case-insensitive language processing

Initial Comment:
Some language identifiers are case-insensitive (as in Fortran and VB), but by default LXR cross-references everything case sensitive.  This patch modifies generic.pm to read a new lang spec option, 'caseinsensitive', and apply to to reading, referencing, and browsing.


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

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

[Lxr-dev] [ lxr-Patches-1832710 ] Add Fortran reserved words, freeform comments, and strings.

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

Patches item #1832710, was opened at 2007-11-15 19:40
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390119&aid=1832710&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: Browsing
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Craig (mr_wednesday)
Assigned to: Nobody/Anonymous (nobody)
Summary: Add Fortran reserved words, freeform comments, and strings.

Initial Comment:
The default generic.conf is very sparse for Fortran.  This patch adds all the reserved words that I can remember for Fortran 95.  It also adds handling for free form comments (fixed form needs a custom parser anyway) and for strings.

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

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

[Lxr-dev] [ lxr-Bugs-1807357 ] MySQL server has gone away at lib/LXR/Index/Mysql.pm line258

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

Bugs item #1807357, was opened at 2007-10-04 09:08
Message generated for change (Comment added) made by mbox
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1807357&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: genxref
Group: v0.9.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: aarunendra (aarunendra)
Assigned to: Nobody/Anonymous (nobody)
Summary: MySQL server has gone away at lib/LXR/Index/Mysql.pm line258

Initial Comment:
I am indexing the Biweekly releases. When I ran the genxref on the smaller releases (Size of the release is less) everything is going fine. For larger releases (more in size) initially for couple of release it worked fine. After that following error is coming while running genxref

------------------------------------------------------
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 201.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 201.
BTYPE was: atom
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 204.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 204.
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 204.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 204.
BTYPE was: atom
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 206.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 206.
BTYPE was: atom
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 208.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 208.
BTYPE was: atom

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

Identifier search is not working 

Can some one help how to overcome the above problem.

Thanks


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

>Comment By: Malcolm Box (mbox)
Date: 2007-10-04 21:45

Message:
Logged In: YES 
user_id=215386
Originator: NO

Looks like your MySQL server has crashed, or the DBI driver to it has lost
the connection.

I suggest checking your mysql logs to see what's happening.


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

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

[Lxr-dev] [ lxr-Bugs-1807357 ] MySQL server has gone away at lib/LXR/Index/Mysql.pm line258

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

Bugs item #1807357, was opened at 2007-10-04 09:08
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1807357&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: genxref
Group: v0.9.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: aarunendra (aarunendra)
Assigned to: Nobody/Anonymous (nobody)
Summary: MySQL server has gone away at lib/LXR/Index/Mysql.pm line258

Initial Comment:
I am indexing the Biweekly releases. When I ran the genxref on the smaller releases (Size of the release is less) everything is going fine. For larger releases (more in size) initially for couple of release it worked fine. After that following error is coming while running genxref

------------------------------------------------------
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 201.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 201.
BTYPE was: atom
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 204.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 204.
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 204.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 204.
BTYPE was: atom
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 206.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 206.
BTYPE was: atom
DBD::mysql::st execute failed: MySQL server has gone away at lib/LXR/Index/Mysql.pm line 258, <GEN537963> line 208.
DBD::mysql::st fetchrow_array failed: fetch() without execute() at lib/LXR/Index/Mysql.pm line 259, <GEN537963> line 208.
BTYPE was: atom

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

Identifier search is not working 

Can some one help how to overcome the above problem.

Thanks


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

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

[Lxr-dev] [ lxr-Bugs-1209273 ] "release" a reserved word in MySQL 5.x

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

Bugs item #1209273, was opened at 2005-05-26 16:33
Message generated for change (Comment added) made by stemcel
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=390117&aid=1209273&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: Open
Resolution: Accepted
Priority: 5
Private: No
Submitted By: Jeff Warnica (jeffwarnica)
Assigned to: Malcolm Box (mbox)
Summary: "release" a reserved word in MySQL 5.x

Initial Comment:
And perhaps earlier versions too.

The table lxr_releases can not be created..

The MySQL docs claim that you can use reserved words as
identifiers if you quote them, but testing the CREATE
TABLE with "release" quoted also failed. 

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

Comment By: Joshua Barr (stemcel)
Date: 2007-07-26 22:04

Message:
Logged In: YES 
user_id=1838421
Originator: NO

Summary says that CREATE TABLE with "release" quoted fails, but you need
to use back ticks (i.e. `release`) to quote the keyword. All instances of
"release" in initdb-mysql and all those that are not Perl scalars in
..../lib/LXR/Index/MySQL.pm need to be quoted or have their names changed.
"release" is not a reserved keyword in MySQL 4.x.

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

Comment By: aaron (ipo23)
Date: 2007-05-13 00:44

Message:
Logged In: YES 
user_id=1619342
Originator: NO

same here - aaron@texas:/usr/share/doc/lxr-cvs/examples$ mysql --version
mysql  Ver 14.12 Distrib 5.0.38, for pc-linux-gnu (x86_64) using readline
5.2
aaron@texas:/usr/share/doc/lxr-cvs/examples$ 

release needs to be quoted with backquotes as a field definition as well
as in the primary key clause
then it works

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

Comment By: Brian St. Pierre (bstpierre)
Date: 2006-10-06 17:40

Message:
Logged In: YES 
user_id=10357

Looking in CVS, it doesn't appear that the patch was applied to Mysql.pm.
(I do see the change in initdb-mysql.)

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

Comment By: Danny (perunaion)
Date: 2006-09-16 02:20

Message:
Logged In: YES 
user_id=1047608

Release 1559658, attempts to address this issue.
Its a patch of the two modified files (Mysql.pm and
initdb-mysql).  Hopefully that will help fix this.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2006-07-13 23:59

Message:
Logged In: NO 

You need to change BOTH the initdb-mysql script and the
Mysql.pm module (8 occurrences total).  You can either
change the name of the 'release' field (which was the route
I took), or quote it with back-ticks.

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

Comment By: Laurence Passmore (lmop)
Date: 2006-06-07 08:25

Message:
Logged In: YES 
user_id=1410237

I think you need to change lib/LXR/Index/Mysql.pm thus:

1) s/r.release/r.`release`/g

2) s/release =/`release` =/g

3) s/ release\)/ `release`\)/g

(I say think because I haven't tested it; I currently have other issues
with my LXR 
installation that is preventing me from getting it working at all...)

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

Comment By: Malcolm Box (mbox)
Date: 2006-06-06 22:24

Message:
Logged In: YES 
user_id=215386

Apparently not a good fix - reopening

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

Comment By: Malcolm Box (mbox)
Date: 2006-06-05 10:16

Message:
Logged In: YES 
user_id=215386

Now fixed in CVS. Thanks to lmop for the fix.

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

Comment By: S Melody (prplehaze2)
Date: 2006-05-31 15:37

Message:
Logged In: YES 
user_id=911986

I used this fix to create the tables, but indexing seems to
fail, most likely because release is a reserved word:

DBD::mysql::st execute failed: 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 'release =
'head'' at line 1 at lib/LXR/Index/Mysql.pm line 209.
DBD::mysql::st execute failed: 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 'release)
values ('387', 'head')' at line 1 at lib/LXR/Index/Mysql.pm
line 213.


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

Comment By: Laurence Passmore (lmop)
Date: 2005-12-21 17:20

Message:
Logged In: YES 
user_id=1410237

This is a simple fix. initdb-mysql should be changed as follows
(basically, 
backtick (`) the column name `release` to escape/quote it):

create table lxr_releases (
        fileid          int not null references lxr_files,
        `release`       char(255) binary not null,
        primary key     (fileid, `release`)
);

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

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

Re: [Lxr-dev] Updates?

[Paul S. <ps...@ne...>]

On Wed, 2007-06-27 at 22:37 +0200, Arne Georg Gleditsch wrote:
> Thanks, I remember reading it now.  Yes, I agree that independent
> objects per file is the way to go.  It's what I've got in my tree,
> anyway.

If you've already done work like this then definitely I'd like to see
your stuff before committing lots more effort to modifying the existing
LXR.

-- 
-----------------------------------------------------------------------------
 Paul D. Smith <ps...@ne...>                       http://netezza.com
 "Please remain calm--I may be mad, but I am a professional."--Mad Scientist
-----------------------------------------------------------------------------
      These are my opinions--Netezza takes no responsibility for them.

Re: [Lxr-dev] Updates?

[Arne G. G. <ar...@gl...>]

Paul Smith wrote:
> On Mon, 2007-06-25 at 10:47 +0200, Arne Georg Gleditsch wrote:
>>> (b) cleaning up the class interface to the back ends to allow new
>>> ones to be more cleanly created (I have at least on back end that
>>> I'd like to write, that is tricky with the current interface)
> 
>>  (I'd be interested in hearing more about your specific concerns
>> regarding (b), though.)
> 
> There's an email from me whinging about the structure of the File
> backend class interface and burbling about the way I would prefer to see
> it structured.  Let me look... start here for example:
> 
> http://sourceforge.net/mailarchive/message.php?msg_name=1174269877.16513.12.camel%40homebase

Thanks, I remember reading it now.  Yes, I agree that independent
objects per file is the way to go.  It's what I've got in my tree, anyway.

-- 
							Arne.

Re: [Lxr-dev] Updates?

[Paul S. <ps...@ne...>]

On Mon, 2007-06-25 at 10:47 +0200, Arne Georg Gleditsch wrote:
> > (b) cleaning up the class interface to the back ends to allow new
> > ones to be more cleanly created (I have at least on back end that
> > I'd like to write, that is tricky with the current interface)

>  (I'd be interested in hearing more about your specific concerns
> regarding (b), though.)

There's an email from me whinging about the structure of the File
backend class interface and burbling about the way I would prefer to see
it structured.  Let me look... start here for example:

http://sourceforge.net/mailarchive/message.php?msg_name=1174269877.16513.12.camel%40homebase

-- 
-----------------------------------------------------------------------------
 Paul D. Smith <ps...@ne...>                       http://netezza.com
 "Please remain calm--I may be mad, but I am a professional."--Mad Scientist
-----------------------------------------------------------------------------
      These are my opinions--Netezza takes no responsibility for them.

[Lxr-dev] OT: Invitation to participate in research project

[Ben A. <ben...@st...>]

Hello there

I would greatly appreciate a small amount of your time to assist with
my doctoral research at The University of Newcastle. The research
concerns open source licensing and we're seeking developers working on
Java projects. The research is supervised, ethics-approved, anonymous
and results will be freely available. Participation will also provide a
custom licensing report for your project. To learn more, please visit:

   http://licensing-research.newcastle.edu.au

Thanks for reading this email, and I hope you'll consider participating.

Best regards
Ben Alex

(My apologies for being off-topic; this list will not be emailed again)

Re: [Lxr-dev] Updates?

[Arne G. G. <ar...@gl...>]

Jan-Benedict Glaw wrote:
> Dito.  This is why we started the drop-down thingie for versions at
> some time. Max has the most up-to-date patches.  Worked mostly, IIRC,
> but ISTR a problem with /diff.

As it is, the diff functionality depends on the different "axis" defined
for a tree (which are usually "version" and "arch", since that's what
the default config uses).  I've come to think this is broken.  I'd like
to see your browsing history available as a drop-down, where you can
choose to diff the currently viewed file against any of the, say, 5 last
files you've visited in the current tree.  I want to toss out the
user-defineable variables altogether, and just keep "version" as an
integral component.  I think they clutter up the interface, are not
horribly useful and, in the rare cases where they could be useful, are
too complicated to actually use.

-- 
								Arne.

Re: [Lxr-dev] Updates?

[Jan-Benedict G. <jb...@lu...>]

On Mon, 2007-06-25 10:47:47 +0200, Arne Georg Gleditsch <ar...@gl...> w=
rote:
> index for every release.  (My ambition is to have all 7-800 releases of
> the Linux kernel referenced and indexed on lxr.linux.no.)  Xapian also

Dito.  This is why we started the drop-down thingie for versions at
some time. Max has the most up-to-date patches.  Worked mostly, IIRC,
but ISTR a problem with /diff.

MfG, JBG

--=20
      Jan-Benedict Glaw      jb...@lu...              +49-172-7608481
Signature of:                 Gib Dein Bestes. Dann =C3=BCbertriff Dich sel=
bst!
the second  :

Re: [Lxr-dev] Updates?

[Arne G. G. <ar...@gl...>]

Paul Smith wrote:
> Also, I second Max's interest in seeing the code changes, or at least a
> list of enhancements/changes.  I don't know if you've had a chance to
> follow some of the modifications I was suggesting a month or two ago,
> but I wonder if any of your changes are in those areas.

Yes, some of them are.  One of my main concerns have been scalability,
genxref-time, so there are a couple of changes in that area.  I'm using
postgres' copy for populating some of the tables, for instance.  Also,
the freetext indexes are incremental (using Xapian) in the hope that
this will scale better (both run-time and space-wise) than one full
index for every release.  (My ambition is to have all 7-800 releases of
the Linux kernel referenced and indexed on lxr.linux.no.)  Xapian also
makes it easier to provide line number information with the search
results.  The identifier lookups attempt to consider the scope of the
reference you're following.  The web interface has been redone.

> My main interest at this time is (a) collecting the various bug fixes
> that are going around and integrating those, (b) cleaning up the class
> interface to the back ends to allow new ones to be more cleanly created
> (I have at least on back end that I'd like to write, that is tricky with
> the current interface), and obviously (c) getting a new release out
> there.

I agree with your agenda.  Also, if you want to get a release out the
door as soon as possible, I'd suggest you ignore me for the time being.
 (I'd be interested in hearing more about your specific concerns
regarding (b), though.)

-- 
								Arne.

Re: [Lxr-dev] Updates?

[Arne G. G. <ar...@gl...>]

(Sorry about the delay; real life intervened...)

Maximilian Wilhelm wrote:
> Can you put your Code into a public accessable GIT or something else,
> so one can pull your version an have a look at the changes?

For sure.  lxr.linux.no is due to move to new, dedicated hw in the near
future, and I was hoping to put up a beta version with source and the
like on that one.  I was hoping to have this done by now, actually.  If
it looks to take much more time, I'll put the source up somewhere else
in the meantime.

-- 
								Arne.

Re: [Lxr-dev] Updates?

[Paul S. <ps...@ne...>]

On Mon, 2007-06-18 at 16:45 +0200, Arne Georg Gleditsch wrote:
> Paul Smith wrote:
> > I would love to do some more work on LXR but I really don't want to get
> > too far out in front of the official codebase; my experiences with this
> > have been universally negative (more work for everyone, in the best
> > case).
> 
> On this tangent: in the process of trying to resolve my own scalability
> issues with lxr.linux.no, I have a private lxr codebase that has
> diverged non-trivially from mainline.  (And I do regret that, my
> experience is in line with Paul's here...)  Still, I do hope to put this
> into production on lxr.linux.no in the near future.  Once that happens,
> I'd be interested in assessing the actual gap to mainline, but in the
> mean time the code lives in a private repository of mine under the name
> "lxrng".  If any of the movers and shakers in the lxr-mainline camp feel
> uncomfortable with me using this name in public as well, I'd like to
> know.  I do feel I have a certain historical claim to the "lxr" name,
> but at the same time I'd like to avoid stepping on peoples toes.

My only concern about this is that if LXR does manage to bring your
enhancements back into the main codebase (as hopefully it will!) then
we'll have an "lxrng" which is less up to date than the main "lxr",
which would be confusing to all I would imagine.

Maybe we can find a less evocative name, something like "lxralt" or
"linxr" or something like that, that doesn't imply "next
generation" (even if, for the time being at least, it really is!)
Ultimately, however, it doesn't bother me much either way.  Whatever
happens will be survivable.


Also, I second Max's interest in seeing the code changes, or at least a
list of enhancements/changes.  I don't know if you've had a chance to
follow some of the modifications I was suggesting a month or two ago,
but I wonder if any of your changes are in those areas.

My main interest at this time is (a) collecting the various bug fixes
that are going around and integrating those, (b) cleaning up the class
interface to the back ends to allow new ones to be more cleanly created
(I have at least on back end that I'd like to write, that is tricky with
the current interface), and obviously (c) getting a new release out
there.

(c) might most profitably be done multiple times (once after (a) and
again after (b) for example).


Cheers!

-- 
-----------------------------------------------------------------------------
 Paul D. Smith <ps...@ne...>                       http://netezza.com
 "Please remain calm--I may be mad, but I am a professional."--Mad Scientist
-----------------------------------------------------------------------------
      These are my opinions--Netezza takes no responsibility for them.

Re: [Lxr-dev] Updates?

[Maximilian W. <ma...@rf...>]

Am Monday, den 18 June hub Arne Georg Gleditsch folgendes in die Tasten:

Hi!

> On this tangent: in the process of trying to resolve my own scalability
> issues with lxr.linux.no, I have a private lxr codebase that has
> diverged non-trivially from mainline.  (And I do regret that, my
> experience is in line with Paul's here...)  Still, I do hope to put this
> into production on lxr.linux.no in the near future.  Once that happens,
> I'd be interested in assessing the actual gap to mainline, but in the
> mean time the code lives in a private repository of mine under the name
> "lxrng".  If any of the movers and shakers in the lxr-mainline camp feel
> uncomfortable with me using this name in public as well, I'd like to
> know.  I do feel I have a certain historical claim to the "lxr" name,
> but at the same time I'd like to avoid stepping on peoples toes.

Can you put your Code into a public accessable GIT or something else,
so one can pull your version an have a look at the changes?
You could create a branch pimpMyLxr or so :)

Ciao
Max
-- 
	Follow the white penguin.