Re: [Koha] upgrade from 1.3.2 to 2.0
MJ & Paul: Thanks for your suggestions! I now have Koha about 90% up and running. The OPAC works OK (including search), and many of the Intranet functions work OK - Our data is there, and we have MARC tags! The remaining problem is that the MARC search does not work - it takes me to a white error page. The MARC search categories are there, it just doesn't do the search. I assume this has something to do with MARC configuration. I checked the Koha error log, and found this: Can't use an undefined value as a HASH reference at /usr/local/koha/intranet/modules/C4/SearchMarc.pm line 116. [Thu Jul 1 11:00:04 2004] [error] [client 192.168.0.5] Premature end of script headers: /usr/local/koha/intranet/cgi-bin/search.marc/search.pl Does this ring any bells? Is there something I am obviously not doing? How do I define the value for the HASH reference? Robert
Have you got your branches set up, and do the items have homebranches set? It sounds like Koha is having trouble figuring out where your items are (at what location). Stephen Robert Maynord said:
MJ & Paul:
Thanks for your suggestions! I now have Koha about 90% up and running. The OPAC works OK (including search), and many of the Intranet functions work OK - Our data is there, and we have MARC tags!
The remaining problem is that the MARC search does not work - it takes me to a white error page. The MARC search categories are there, it just doesn't do the search. I assume this has something to do with MARC configuration.
I checked the Koha error log, and found this:
Can't use an undefined value as a HASH reference at /usr/local/koha/intranet/modules/C4/SearchMarc.pm line 116. [Thu Jul 1 11:00:04 2004] [error] [client 192.168.0.5] Premature end of script headers: /usr/local/koha/intranet/cgi-bin/search.marc/search.pl
Does this ring any bells? Is there something I am obviously not doing? How do I define the value for the HASH reference?
Robert
-- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges@skemotah.com
On 2004-07-01 18:02:41 +0100 Robert Maynord <rmaynord@ihm-school.org> wrote:
Does this ring any bells? Is there something I am obviously not doing? How do I define the value for the HASH reference?
Do you have stopwords defined? I think they're set in the Parameters section. -- MJR/slef My Opinion Only and not of any group I know http://www.ttllp.co.uk/ for creative copyleft computing "To be English is not to be baneful / To be standing by the flag not feeling shameful / Racist or partial..." (Morrissey)
MJ: This worked! My author name now works - the others are blank, so I assume that is a MARC tag configuration issue. But the MARC search works... Thanks for your help! Robert
On 2004-07-01 18:02:41 +0100 Robert Maynord <rmaynord@ihm-school.org> wrote:
Does this ring any bells? Is there something I am obviously not doing? How do I define the value for the HASH reference?
Do you have stopwords defined? I think they're set in the Parameters section.
Hello. I am migrating the BD mysq Koha to Postgresql, I want to saver if somebody had that experience, I am beginning to modify the copy that I did of the SQL of mysql. To load to poststoneware and to modify the access of the DBI with the Perl. thanks friends.
Mandi! Christian Calle In chel di` si favelave...
I am migrating the BD mysq Koha to Postgresql, I want to saver if somebody had that experience, I am beginning to modify the copy that I did of the SQL of mysql. To load to poststoneware and to modify the access of the DBI with the Perl.
I've also thinked about porting koha to postgres, and AFAIK it is planned in some future release... the problem are not on perl side, where dbi do an exellent work, but on schema and SQL dialects. MySQL accept rather all identifier for field and table name, where postgres are more clever and define as reserved all the SQL92 identifier (as standard say) and some more. So, it is needed to change the schema, because there's no way to create a field name ``user'' or ``desc'' in postgres, for example... The second big problem came again from the bad adherence of mysql to the SQL standards: MySQL accept rather all SQL syntiax (sometime ignoring it ;) but have some custom instructions like... mumble... i don't remember, could be ADD? In any case, an instruction that alter a record, if present, or insert if not. So i think that porting koha to postgres will be a very cool feature, but expect to: 1) alter the schema 2) alter some sql instruction (for 1) 3) alter the code to substitute a non-standard sql instruction with some standard ones, plus some code. Good luck. ;) -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia'' http://www.sv.lnf.it/ Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN) gaio(at)sv.lnf.it tel +39-0434-842711 fax +39-0434-842797 ... votantoniovotantoniovotantoniovotantoniovotantoniovotantonio ... resistenza arcobaleno contro la politica grigia http://www.peacelink.it/votantonio
On 2004-07-07 10:29:14 +0100 Marco Gaiarin <gaio@sv.lnf.it> wrote:
So, it is needed to change the schema, because there's no way to create a field name ``user'' or ``desc'' in postgres, for example...
Sorry, I think that's wrong: test=> create table "gaiotest" ( "user" varchar ); CREATE TABLE test=> You just have to quote it like good SQL. Some of the bad quoting in the current schema (produced by mysql's tools, no less!) have caused problems with some mysql versions, so it should be fixed anyway, else we'll be chasing these bugs forever. -- MJR/slef My Opinion Only and not of any group I know http://www.ttllp.co.uk/ for creative copyleft computing "To be English is not to be baneful / To be standing by the flag not feeling shameful / Racist or partial..." (Morrissey)
Mandi! MJ Ray In chel di` si favelave...
So, it is needed to change the schema, because there's no way to create a field name ``user'' or ``desc'' in postgres, for example... Sorry, I think that's wrong:
Ok, it's true, you can quote the reserved word, but you have to quote also on every sql statement, so you have to alter also all the program. For me it's cleaner to simply rename the field name... altering all the code to put \"user\", or use userid instead of user it's rather the same. ;) [or you are saying me that koha have just all the sql statement correctly escaped/quote-protected, and it is only a matter to alter the schema?] PS: ok, memory came back, the non standard sql instruction that koha (1.2.X) used was REPLACE INTO. ;) -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia'' http://www.sv.lnf.it/ Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN) gaio(at)sv.lnf.it tel +39-0434-842711 fax +39-0434-842797 ... votantoniovotantoniovotantoniovotantoniovotantoniovotantonio ... resistenza arcobaleno contro la politica grigia http://www.peacelink.it/votantonio
Marco Gaiarin a écrit :
PS: ok, memory came back, the non standard sql instruction that koha (1.2.X) used was REPLACE INTO. ;)
It's still in use in some places. In 2.0 there are also fulltext indexes that are not standard SQL. They will be removed in 2.2 (it's used in thesaurus/authorities management, & 2.2 will be full MARC-compliant and won't use anymore fulltext indexes. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
On 2004-07-07 13:23:57 +0100 Marco Gaiarin <gaio@sv.lnf.it> wrote:
Ok, it's true, you can quote the reserved word, but you have to quote also on every sql statement, so you have to alter also all the program.
Of course, but doing not quoting attributes seems to be a bug. Fixing bugs usually has other benefits. In this case, it reduces the tie to particular SQL oddities of some databases, so will probably make porting to other databases easier. -- MJR/slef My Opinion Only and not of any group I know http://www.ttllp.co.uk/ for creative copyleft computing "To be English is not to be baneful / To be standing by the flag not feeling shameful / Racist or partial..." (Morrissey)
participants (6)
-
Christian Calle -
Marco Gaiarin -
MJ Ray -
Paul POULAIN -
Robert Maynord -
Stephen Hedges