Just an article about MySQL, and a reason to think about PostgreSQL:
http://ostatic.com/blog/the-state-of-postgresql-not-so-easy-to-kil
Some trends: http://www.google.com/trends?q=PostgreSQL%2C+mysql
___
Koha-devel mailing list
Koha-devel@lists.koha.org
h
>
>
> You are right Colin, that way many people who do not have much programming
experience can make a contribution, not expecting to find that the code was
mostly koha perl, my basic rudiments are programming in python, so for now
they work in things that are much more according to my capacities t
On 02/12/09 21:13, Rick Welykochy wrote:
> Joe Atzberger wrote:
>
>> Chris' work is encouraging. ORM classes are definitely a different way
>> of thinking about data though. The mapping is its own little ecosystem,
>> and will require the structure to be maintained and updated (much like
>> kohas
Joe Atzberger wrote:
> Chris' work is encouraging. ORM classes are definitely a different way
> of thinking about data though. The mapping is its own little ecosystem,
> and will require the structure to be maintained and updated (much like
> kohastructure.sql and updatedatabase). One great thi
On Wed, Dec 2, 2009 at 3:00 PM, ricardo mendoza wrote:
> What you mean Joe, is that it's much better to work with a layer of
> abstraction, regardless of the database used.
>
Yes, that's right. So it is better to move in that direction instead of
trying to convert one particular form of SQL to a
Chris, is good to hear this, for a long time I thought that koha never be
able to give full support to postgresql, but I see that this is the way to
get started.
I am reviewing the code of 3.0.4, I want to make some contribution to koha,
but I'm not a professional programmer so I have to start with
What you mean Joe, is that it's much better to work with a layer of
abstraction, regardless of the database used.
Ricardo,
___
Koha-devel mailing list
Koha-devel@lists.koha.org
http://lists.koha.org/mailman/listinfo/koha-devel
2009/12/3 Joe Atzberger :
> This isn't going to happen any time soon, if ever. It is, in my opinion, a
> waste of time to try to convert all the existing SQL statements and
> structure to be both mysql and PG-compatible, leading to a lot of
> duplication in almost every C4 subroutine. In particul
2009/12/3 Joe Atzberger :
> This isn't going to happen any time soon, if ever. It is, in my opinion, a
> waste of time to try to convert all the existing SQL statements and
> structure to be both mysql and PG-compatible, leading to a lot of
> duplication in almost every C4 subroutine. In particul
This isn't going to happen any time soon, if ever. It is, in my opinion, a
waste of time to try to convert all the existing SQL statements and
structure to be both mysql and PG-compatible, leading to a lot of
duplication in almost every C4 subroutine. In particular, such effort could
be more frui
10 matches
Mail list logo
