El 23/03/2012 22:22, Christopher Nighswonger chris.nighswon...@gmail.com
escribió:
On Fri, Mar 23, 2012 at 5:38 PM, Marc Balmer m...@msys.ch 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
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?
Yes, of course.
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
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
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
