Arindam,
Please use the attached schema.sql as a replacement for the one that
came in the 1.8 beta tarball. You can just generate a schema_search.sql
as I indicated previously by running sql/mksearch_schema on it:
perl sql/mksearch_schema sql/schema.sql > sql/schema_search.sql
In your case, assuming nothing important is in your database at this
early stage, you can run, in mysql, "source sql/wipe.sql" in the main
database, which will wipe it and propagate that wipe to the search
database, assuming replication is live, and then you can "use
bibliotech_search" (or whatever you named the search database, i.e. the
MyISAM one) and run "source sql/schema_search.sql" to rebuild it with
FULLTEXT keys.
Martin
Ganguly, Arindam wrote:
Hey Martin,
Wiki-toolkit version 0.74
And no fulltext indexing in the search tables.
-arindam
-----Original Message-----
From: Martin Flack [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 04, 2007 3:26 PM
To: Ganguly, Arindam
Cc: [email protected]
Subject: Re: [Connotea-code-devel] FW: connotea install complete...but
still some errors
Ganguly, Arindam wrote:
undef error - DBD::mysql::st execute failed: Unknown column 'node' in
'where clause' [for Statement "SELECT metadata_type, metadata_value
FROM
metadata WHERE node='User:aganguly' AND version='0'"] at
/usr/local/lib/perl5/site_perl/5.8.8/DBIx/ContextualFetch.pm line 52.
Issue with the wiki-tookkit?
Yes, what version do you have? This should tell you:
perl -MWiki::Toolkit -e 'print $Wiki::Toolkit::VERSION, "\n"'
Note that we don't use CGI::Wiki anymore.
user aganguly (1) requests /search?q=tag bringing load to with db at
1196729034
undef error - DBD::mysql::st execute failed: Can't find FULLTEXT index
matching the column list [for Statement "SELECT ub.user_bookmark_id,
[snip]
I think this might be a bug in the schema in that particular tarball.
You should have a main database with InnoDB tables, and if you want
search to work, a secondary database with MyISAM tables replicating from
the first one. DBI_SEARCH in the config indicates the secondary one.
The schema for the secondary database should be created from the schema
for the primary database with this command:
perl sql/mkschema_search < sql/schema.sql
If that output does not contain FULLTEXT lines like this, then there is
a problem, and I'll have to help:
perl sql/mkschema_search < sql/schema.sql | grep FULLTEXT
,FULLTEXT INDEX `name_ft` (`firstname`, `forename`, `lastname`)
,FULLTEXT INDEX `url_ft` (`url`)
,FULLTEXT INDEX `title_ft` (`title`)
,FULLTEXT INDEX `title_ft` (`title`)
,FULLTEXT INDEX `entry_ft` (`entry`)
,FULLTEXT INDEX `name_ft` (`name`)
,FULLTEXT INDEX `description_ft` (`description`)
,FULLTEXT INDEX `name_ft` (`name`)
,FULLTEXT INDEX `medline_ta_ft` (`medline_ta`)
,FULLTEXT INDEX `name_ft` (`name`)
,FULLTEXT INDEX `title_ft` (`title`)
,FULLTEXT INDEX `description_ft` (`description`)
Martin
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Connotea-code-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/connotea-code-devel
