Begin forwarded message:
> From: luis diaz
> Date: 24 March 2012 12:41:41 AM NZDT
> To: koha-ze...@lists.koha-community.org
> Subject: [Koha-zebra] Apache issue
>
> Hello
>
> I have a rhel6 server (Linux el6.x86_64 #1 SMP Fri Feb 10 15:22:22 EST 2012
> x86_64 x86_64 x86_64 GNU/Linux)
> Red
On 2012-03-22, at 2:22 AM, Liz Rea wrote:
> I have one that is a combo of sample data and MARC21 data - you can get it at
> https://github.com/wizzyrea/Scripts-and-Things/blob/master/kohadev-withbibs.sql.gz
> (do note, it's possible the rules in there are not quite sane or not defined
> in a wa
El 23/03/2012 22:22, "Christopher Nighswonger"
escribió:
>
> On Fri, Mar 23, 2012 at 5:38 PM, Marc Balmer wrote:
> > Am 23.03.12 21:39, schrieb Ian Walls:
> >> Marc,
>
> ...
>
> >
> >> Are there any specific features of PostgreSQL that would lead to a
> >> beneficial new feature for library patro
Tomas,
> >> Are there any specific features of PostgreSQL that would lead to a
> > >> beneficial new feature for library patrons? I know there is plenty of
> > >> literature on it's merits over MySQL, but how do those translate to
> > >> something that the users of Koha can benefit from?
> > >
>
Op 25-03-12 02:28, Jared Camins-Esakov schreef:
> MySQL supports ExtractValue too. Is there something special in the
> Postgres functionality that makes a difference for the end user?
Actually, this is something worth considering when supporting multiple
databases: some reports may require a diffe
Am 24.03.12 14:44, schrieb Robin Sheat:
> Op 25-03-12 02:28, Jared Camins-Esakov schreef:
>> MySQL supports ExtractValue too. Is there something special in the
>> Postgres functionality that makes a difference for the end user?
>
> Actually, this is something worth considering when supporting mul
Op 25-03-12 03:01, Marc Balmer schreef:
> We adress this problem with the DBQ module, which exists to produce
> database specific SQL code when there is no standard way to express sth
> and when there is no way to get it through DBI. See the example we
> bundled with the path in bug 7365.
I'm not
Am 24.03.12 15:07, schrieb Robin Sheat:
> Op 25-03-12 03:01, Marc Balmer schreef:
>> We adress this problem with the DBQ module, which exists to produce
>> database specific SQL code when there is no standard way to express sth
>> and when there is no way to get it through DBI. See the example we
Op 25-03-12 03:19, Marc Balmer schreef:
> No, it does not rewrite any reports. If users enter SQL somewhere, I
> assume they enter proper SQL for their DB server. Which leads to a
OK, so it doesn't address this (quite minor) problem.
> I am considering to write a set of compatability functions
Am 24.03.12 15:35, schrieb Robin Sheat:
> Op 25-03-12 03:19, Marc Balmer schreef:
>> No, it does not rewrite any reports. If users enter SQL somewhere, I
>> assume they enter proper SQL for their DB server. Which leads to a
>
> OK, so it doesn't address this (quite minor) problem.
It would mean
10 matches
Mail list logo
