[Koha-devel] sh: mysql: command not found
Hi, I could install the last version of koha (koha-3.00.01-stable) on Mac os x 10.5.5. But in the third step of the web installation, I get this error : sh: mysql: command not found That is strange as it could connect to the database in the step 2 : Connection established. Database koha exists. User kohaadmin has all required privileges on database koha. This error appears only in the step three while trying to "create the database tables and fill them with some default data" Thanks for yours help, --- Anas___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] sh: mysql: command not found
hello, On Thu, Apr 09, 2009 at 07:49:24PM +0200, Anas Ghrab wrote: > I could install the last version of koha (koha-3.00.01-stable) on Mac os > x 10.5.5. But in the third step of the web installation, I get this > error : sh: mysql: command not found sure: it requires the mysql client (the command line one) to be in the path of your http server (this is a bug due to the koha installer stragegy). > That is strange as it could connect to the database in the step 2 : yes ... because you now use the perl DBI engine that does not need external commands. regards -- Marc Chantreux BibLibre, expert en logiciels libres pour l'info-doc http://biblibre.com ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Working on patch, need translation to french for system preference.
This is great, I appreciate your work. The sys. pref. controls the appearance of a link and the function of the page linked to. Yes, this is about patron fines. With the sys. pref. when the link is clicked the page presents a form to change the information of the associated fine, the description, amount, and amount outstanding. Please let me know if this information will effect the translation. Thanks again. On Fri, 2009-04-10 at 08:32 +0200, Nicolas Morin wrote: > On Thu, Apr 9, 2009 at 7:08 PM, Michael Hafen > wrote: > > I'm working on a feature controlled by a sys pref. ( It will default to > > off ). Can someone translate this text to French for inclusion in the > > sysprefs.sql. Thanks. > > > > 'If ON Patron account lines can be changed in the staff client' > > Hi Michael, > I guess I'd need to now more about what the "account lines" referred > to here are to provide a reliable translation. Nevertheless, assuming > they are the fines and the ability to edit them in the staff interface > (?) : "Si activé, permet de modifier les amendes dans l'interface > professionnelle". > I'd like details on the syspref though, not being quite sure I > understand how it works. Thus not quite sure of the accuracy of the > translation. > Thanks, > Nicolas > > > > > > > > > > > -- > > Michael Hafen > > Systems Analyst and Programmer > > Washington County School District > > Utah, USA > > > > for Koha checkout > > http://koha-dev.washk12.org > > or > > git://koha-dev.washk12.org/koha > > > > ___ > > Koha-devel mailing list > > Koha-devel@lists.koha.org > > http://lists.koha.org/mailman/listinfo/koha-devel > > > > > > > -- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://development.washk12.org/gitweb/ or git://development.washk12.org/koha ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Working on patch, need translation to french for system preference.
On Fri, Apr 10, 2009 at 5:11 PM, Michael Hafen wrote: > This is great, I appreciate your work. > > The sys. pref. controls the appearance of a link and the function of the > page linked to. Yes, this is about patron fines. With the sys. pref. > when the link is clicked the page presents a form to change the > information of the associated fine, the description, amount, and amount > outstanding. > > Please let me know if this information will effect the translation. No, that's fine : the translation stands. Does this mean that with the sys pref OFF one cannot manage fines anymore? Hum, it's friday, I'm slow : I'm not sure I get it yet. Nevermind. Nicolas > Thanks again. > > On Fri, 2009-04-10 at 08:32 +0200, Nicolas Morin wrote: >> On Thu, Apr 9, 2009 at 7:08 PM, Michael Hafen >> wrote: >> > I'm working on a feature controlled by a sys pref. ( It will default to >> > off ). Can someone translate this text to French for inclusion in the >> > sysprefs.sql. Thanks. >> > >> > 'If ON Patron account lines can be changed in the staff client' >> >> Hi Michael, >> I guess I'd need to now more about what the "account lines" referred >> to here are to provide a reliable translation. Nevertheless, assuming >> they are the fines and the ability to edit them in the staff interface >> (?) : "Si activé, permet de modifier les amendes dans l'interface >> professionnelle". >> I'd like details on the syspref though, not being quite sure I >> understand how it works. Thus not quite sure of the accuracy of the >> translation. >> Thanks, >> Nicolas >> >> >> >> >> >> >> >> > >> > -- >> > Michael Hafen >> > Systems Analyst and Programmer >> > Washington County School District >> > Utah, USA >> > >> > for Koha checkout >> > http://koha-dev.washk12.org >> > or >> > git://koha-dev.washk12.org/koha >> > >> > ___ >> > Koha-devel mailing list >> > Koha-devel@lists.koha.org >> > http://lists.koha.org/mailman/listinfo/koha-devel >> > >> > >> >> >> > -- > Michael Hafen > Systems Analyst and Programmer > Washington County School District > Utah, USA > > for Koha checkout > http://development.washk12.org/gitweb/ > or > git://development.washk12.org/koha > > -- Nicolas Morin Mobile: +33(0)633 19 11 36 http://www.biblibre.com ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Working on patch, need translation to french for system preference.
The confusion is a flaw in my description. There is a page load when the 'Edit' link is clicked. With the sys. pref. off the link doesn't appear. The link directs to a separate page which also checks the sys. pref. for security sake. Managing fines with this off should be as normal, hence the sys. pref. defaulting to off. This patch is for people who don't care about proper accounting practices. :) On Fri, 2009-04-10 at 17:58 +0200, Nicolas Morin wrote: > On Fri, Apr 10, 2009 at 5:11 PM, Michael Hafen > wrote: > > This is great, I appreciate your work. > > > > The sys. pref. controls the appearance of a link and the function of the > > page linked to. Yes, this is about patron fines. With the sys. pref. > > when the link is clicked the page presents a form to change the > > information of the associated fine, the description, amount, and amount > > outstanding. > > > > Please let me know if this information will effect the translation. > > No, that's fine : the translation stands. > Does this mean that with the sys pref OFF one cannot manage fines > anymore? Hum, it's friday, I'm slow : I'm not sure I get it yet. > Nevermind. > Nicolas > > [snip] > >> (?) : "Si activé, permet de modifier les amendes dans l'interface > >> professionnelle". On another note would someone please comment on how this compares to Francis Wanga's translation. I have to ability to choose between the two. Thanks. On Fri, 2009-04-10 at 07:13 +0200, Francis WANGA wrote: > > I'm working on a feature controlled by a sys pref. ( It will default > to > > off ). Can someone translate this text to French for inclusion in > the > > sysprefs.sql. Thanks. > > > > 'If ON Patron account lines can be changed in the staff client' > > Autorise la modification des lignes de compte des emprunteurs > > Thanks. > -- > Francis -- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://development.washk12.org/gitweb/ or git://development.washk12.org/koha ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Working on patch, need translation to french for system preference.
On Fri, Apr 10, 2009 at 6:15 PM, Michael Hafen wrote: > The confusion is a flaw in my description. There is a page load when > the 'Edit' link is clicked. With the sys. pref. off the link doesn't > appear. The link directs to a separate page which also checks the sys. > pref. for security sake. > > Managing fines with this off should be as normal, hence the sys. pref. > defaulting to off. This patch is for people who don't care about proper > accounting practices. :) OK, so my translation is NOT good after all. Francis' better, expect we chose globally to translate patrons as "adhérents" rather than "emprunteurs". So that would be : "Autorise la modification des lignes de compte des adhérents" Nicolas > > On Fri, 2009-04-10 at 17:58 +0200, Nicolas Morin wrote: >> On Fri, Apr 10, 2009 at 5:11 PM, Michael Hafen >> wrote: >> > This is great, I appreciate your work. >> > >> > The sys. pref. controls the appearance of a link and the function of the >> > page linked to. Yes, this is about patron fines. With the sys. pref. >> > when the link is clicked the page presents a form to change the >> > information of the associated fine, the description, amount, and amount >> > outstanding. >> > >> > Please let me know if this information will effect the translation. >> >> No, that's fine : the translation stands. >> Does this mean that with the sys pref OFF one cannot manage fines >> anymore? Hum, it's friday, I'm slow : I'm not sure I get it yet. >> Nevermind. >> Nicolas >> >> > [snip] >> >> (?) : "Si activé, permet de modifier les amendes dans l'interface >> >> professionnelle". > > On another note would someone please comment on how this compares to > Francis Wanga's translation. I have to ability to choose between the > two. Thanks. > > On Fri, 2009-04-10 at 07:13 +0200, Francis WANGA wrote: >> > I'm working on a feature controlled by a sys pref. ( It will default >> to >> > off ). Can someone translate this text to French for inclusion in >> the >> > sysprefs.sql. Thanks. >> > >> > 'If ON Patron account lines can be changed in the staff client' >> >> Autorise la modification des lignes de compte des emprunteurs >> >> Thanks. >> -- >> Francis > > -- > Michael Hafen > Systems Analyst and Programmer > Washington County School District > Utah, USA > > for Koha checkout > http://development.washk12.org/gitweb/ > or > git://development.washk12.org/koha > > -- Nicolas Morin Mobile: +33(0)633 19 11 36 http://www.biblibre.com ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Working on patch, need translation to french for system preference.
Thank you Nicolas. I'll use this translation then. On another note, I'm wondering about the single quote. The SQL doesn't like it in "l'interface". To work in the SQL should that be "l''interface"? I ask because I see something similar on another line of the unimarc_standard_systempref.sql file, line 15. It's about the autoBarcode sys. pref. On Fri, 2009-04-10 at 18:50 +0200, Nicolas Morin wrote: > On Fri, Apr 10, 2009 at 6:15 PM, Michael Hafen > wrote: > > The confusion is a flaw in my description. There is a page load when > > the 'Edit' link is clicked. With the sys. pref. off the link doesn't > > appear. The link directs to a separate page which also checks the sys. > > pref. for security sake. > > > > Managing fines with this off should be as normal, hence the sys. pref. > > defaulting to off. This patch is for people who don't care about proper > > accounting practices. :) > > OK, so my translation is NOT good after all. > Francis' better, expect we chose globally to translate patrons as > "adhérents" rather than "emprunteurs". So that would be : "Autorise la > modification des lignes de compte des adhérents" > > Nicolas > -- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://development.washk12.org/gitweb/ or git://development.washk12.org/koha ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Working on patch, need translation to french for system preference.
Speaking with zero authority on proper usage in French, you might try a backtick instead. On Fri, Apr 10, 2009 at 12:59 PM, Michael Hafen wrote: > Thank you Nicolas. I'll use this translation then. > > On another note, I'm wondering about the single quote. The SQL doesn't > like it in "l'interface". To work in the SQL should that be > "l''interface"? I ask because I see something similar on another line > of the unimarc_standard_systempref.sql file, line 15. It's about the > autoBarcode sys. pref. > > On Fri, 2009-04-10 at 18:50 +0200, Nicolas Morin wrote: > > On Fri, Apr 10, 2009 at 6:15 PM, Michael Hafen > wrote: > > > The confusion is a flaw in my description. There is a page load when > > > the 'Edit' link is clicked. With the sys. pref. off the link doesn't > > > appear. The link directs to a separate page which also checks the sys. > > > pref. for security sake. > > > > > > Managing fines with this off should be as normal, hence the sys. pref. > > > defaulting to off. This patch is for people who don't care about > proper > > > accounting practices. :) > > > > OK, so my translation is NOT good after all. > > Francis' better, expect we chose globally to translate patrons as > > "adhérents" rather than "emprunteurs". So that would be : "Autorise la > > modification des lignes de compte des adhérents" > > > > Nicolas > > > > -- > Michael Hafen > Systems Analyst and Programmer > Washington County School District > Utah, USA > > for Koha checkout > http://development.washk12.org/gitweb/ > or > git://development.washk12.org/koha > ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] Working on patch, need translation to french for system preference.
That is certainly valid SQL ( I just tried it ). Which leaves the question of it being proper French. I suggested the two single-quotes because I noticed that had been done somewhere else in that file. I'm open to either method though. Comments please. On Fri, 2009-04-10 at 13:18 -0400, Joe Atzberger wrote: > Speaking with zero authority on proper usage in French, you might try > a backtick instead. > > On Fri, Apr 10, 2009 at 12:59 PM, Michael Hafen > wrote: > Thank you Nicolas. I'll use this translation then. > > On another note, I'm wondering about the single quote. The > SQL doesn't > like it in "l'interface". To work in the SQL should that be > "l''interface"? I ask because I see something similar on > another line > of the unimarc_standard_systempref.sql file, line 15. It's > about the > autoBarcode sys. pref. > > On Fri, 2009-04-10 at 18:50 +0200, Nicolas Morin wrote: > > On Fri, Apr 10, 2009 at 6:15 PM, Michael Hafen > wrote: > > > The confusion is a flaw in my description. There is a > page load when > > > the 'Edit' link is clicked. With the sys. pref. off the > link doesn't > > > appear. The link directs to a separate page which also > checks the sys. > > > pref. for security sake. > > > > > > Managing fines with this off should be as normal, hence > the sys. pref. > > > defaulting to off. This patch is for people who don't > care about proper > > > accounting practices. :) > > > > OK, so my translation is NOT good after all. > > Francis' better, expect we chose globally to translate > patrons as > > "adhérents" rather than "emprunteurs". So that would be : > "Autorise la > > modification des lignes de compte des adhérents" > > > > Nicolas > > > > > -- > Michael Hafen > Systems Analyst and Programmer > Washington County School District > Utah, USA > > for Koha checkout > http://development.washk12.org/gitweb/ > or > git://development.washk12.org/koha > -- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://development.washk12.org/gitweb/ or git://development.washk12.org/koha ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] [Koha] null itemnumbers and borrowernumbers in issues table
2009/4/11 Joe Atzberger : > > > On Fri, Apr 10, 2009 at 11:19 AM, Jeffrey LePage > wrote: >> >> Greetings, >> >> We've just discovered 4 records in the issues table that have nulls where >> there should never be nulls. Specifically, 2 records with null >> borrowernumber and 2 records with null itemnumber. As a result, there are >> two overdue books checked out to a NULL patron and two patrons who've >> checked out NULL books. >> >> I notice that the issues table is constructed thus: >> mysql> desc issues; >> +-+-+--+-+---+---+ >> | Field | Type | Null | Key | Default | Extra | >> +-+-+--+-+---+---+ >> | borrowernumber | int(11) | YES | MUL | NULL | | >> | itemnumber | int(11) | YES | MUL | NULL | | >> | date_due | date | YES | | NULL | | >> | branchcode | varchar(10) | YES | | NULL | | >> | issuingbranch | varchar(18) | YES | | NULL | | >> | returndate | date | YES | | NULL | | >> | lastreneweddate | date | YES | | NULL | | >> | return | varchar(4) | YES | | NULL | | >> | renewals | tinyint(4) | YES | | NULL | | >> | timestamp | timestamp | NO | | CURRENT_TIMESTAMP | | >> | issuedate | date | YES | | NULL | | >> +-+-+--+-+---+---+ >> >> Notice that borrowernumber and itemnumber are NULL'able. >> Isn't this a _bad_ idea? I don't know why/how the null itemnumbers and >> borrowernumbers got into the database, but it seems that making them >> non-nullable would be a good idea. >> >> Comments? > > This is a known issue, basically a compromise to allow offline circulation > to work in 3.0 (where the borrowernumber or itemnumber might not actually > exist when the insertions are done). But in short, yes, I agree DB > constraints need to be imposed for itemnumber and borrowernumber in issues. Shifting to the devel list. Shouldn't we store the offline circs in their own table, with nullable fields if they need it. Then reconcile them into the issues table? That way we can put the constraints back on the issues table. Chris ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
Re: [Koha-devel] [Koha] null itemnumbers and borrowernumbers in issues table
The moment of upload should catch failed insertions, optionally saving them in a secondary table as described, with feedback to the user. Itemnumber really shouldn't be NULLable at all, since there isn't any point tracking the transaction if you don't know what it is. You won't even know what rule to have circ'd it under. The error message will be more useful than the mangled transaction line. --joe On Fri, Apr 10, 2009 at 3:29 PM, Chris Cormack wrote: > 2009/4/11 Joe Atzberger : > > > > > > On Fri, Apr 10, 2009 at 11:19 AM, Jeffrey LePage < > jeffrey_lep...@yahoo.com> > > wrote: > >> > >> Greetings, > >> > >> We've just discovered 4 records in the issues table that have nulls > where > >> there should never be nulls. Specifically, 2 records with null > >> borrowernumber and 2 records with null itemnumber. As a result, there > are > >> two overdue books checked out to a NULL patron and two patrons who've > >> checked out NULL books. > >> > >> I notice that the issues table is constructed thus: > >> mysql> desc issues; > >> > +-+-+--+-+---+---+ > >> | Field | Type| Null | Key | Default | Extra > | > >> > +-+-+--+-+---+---+ > >> | borrowernumber | int(11) | YES | MUL | NULL | > | > >> | itemnumber | int(11) | YES | MUL | NULL | > | > >> | date_due| date| YES | | NULL | > | > >> | branchcode | varchar(10) | YES | | NULL | > | > >> | issuingbranch | varchar(18) | YES | | NULL | > | > >> | returndate | date| YES | | NULL | > | > >> | lastreneweddate | date| YES | | NULL | > | > >> | return | varchar(4) | YES | | NULL | > | > >> | renewals| tinyint(4) | YES | | NULL | > | > >> | timestamp | timestamp | NO | | CURRENT_TIMESTAMP | > | > >> | issuedate | date| YES | | NULL | > | > >> > +-+-+--+-+---+---+ > >> > >> Notice that borrowernumber and itemnumber are NULL'able. > >> Isn't this a _bad_ idea? I don't know why/how the null itemnumbers and > >> borrowernumbers got into the database, but it seems that making them > >> non-nullable would be a good idea. > >> > >> Comments? > > > > This is a known issue, basically a compromise to allow offline > circulation > > to work in 3.0 (where the borrowernumber or itemnumber might not actually > > exist when the insertions are done). But in short, yes, I agree DB > > constraints need to be imposed for itemnumber and borrowernumber in > issues. > > Shifting to the devel list. > > Shouldn't we store the offline circs in their own table, with nullable > fields if they need it. Then reconcile them into the issues table? > That way we can put the constraints back on the issues table. > > Chris > ___ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
