"Joshua Ferraro" <[EMAIL PROTECTED]> wrote: [...]
> has graciously offered to host a Mailman installation for such lists, so the
> question arises, what domain shall we use? [...]
lists.koha.org would seem to make most sense to me, for similar
reasons to those attributed to Paul.
Is a better list
Thanks,
That's done it.
Harry
Joshua Ferraro wrote:
On 3/1/08, harry wykman <[EMAIL PROTECTED]> wrote:
Thanks Josh for your help.
I am posting to the devel list. As you know, still having the error below
when using standard install.
Harry
Hi Harry,
Please post any questions you
Hi all!
Speaking of Koha 3...
Are items and biblioitems tables modern and old version of the same "what we
want" thing, respectively, or are they complementary tables and both must
exist in Koha 3?
The doubt comes after purging (truncating, really) biblioitems table, and
constating I obtain same
Ignacio Javier a écrit :
> Hi all!
>
> Speaking of Koha 3...
>
> Are items and biblioitems tables modern and old version of the same "what we
> want" thing, respectively, or are they complementary tables and both must
> exist in Koha 3?
>
> The doubt comes after purging (truncating, really) biblioi
Hi All,
When installing Koha 3.00 alpha, I let it install some optional data
(patron types and libraries etc.) so that I could see what they looked
like while adding my own information.
I'm finding that some of them are can not be removed. Is this normal?
For instance some of the branches,
This is probably because if foreign key constraints. I ran into that
myself. I had to delete all the patrons that were in the branch or
patron category first.
On Tue, 2008-03-04 at 08:30 +0900, Ramon Andinach wrote:
> Hi All,
>
> When installing Koha 3.00 alpha, I let it install some optional d
Maybe it's just me, but when I pulled down the patron images patch with
the database create table it didn't hit the installer page to do the
database update. I looked at the updatedatabase.pl file, and it seems
that the patronimages update ended up with the same DBversion as the
previous update.
>Maybe something should be done to make sure that doesn't happen. It
> seems like a tough problem to handle though. Could just skip a version
> number or two to leave space for other developers, but then the
> installer would have to check to make sure that previous updates were
> run for sure.
>
> Would it be possible to start inserting some developer specific part (say,
> part of the MAC address in decimal form) into the DB version? This would at
> least make them unique.
Basically I just have to check better when doing my QA on patches :)
Ive fixed the problem and sent a patch up to
On Mon, Mar 3, 2008 at 6:39 PM, Michael Hafen <[EMAIL PROTECTED]> wrote:
> Maybe it's just me, but when I pulled down the patron images patch with
> the database create table it didn't hit the installer page to do the
> database update. I looked at the updatedatabase.pl file, and it seems
> tha
10 matches
Mail list logo
