On Sun, 2008-05-25 at 11:08 +0200, Sigurd Nes wrote:
> > From: Dave Hall [EMAIL PROTECTED]
> > Sent: 2008-05-25 00:40:03 CEST
> > To: phpgroupware-developers@gnu.org
> > Subject: Re: [phpGroupWare-developers] Nested db-objects
> >
> > ?This is not as Sigurd s
> From: Dave Hall [EMAIL PROTECTED]
> Sent: 2008-05-25 00:40:03 CEST
> To: phpgroupware-developers@gnu.org
> Subject: Re: [phpGroupWare-developers] Nested db-objects
>
> ?This is not as Sigurd suggests a recent change. The change was merged
> into the phpGW tree 6 months ago
This might be a repost (was disconnected).
> From: Dave Hall [EMAIL PROTECTED]
> Sent: 2008-05-25 00:40:03 CEST
> To: phpgroupware-developers@gnu.org
> Subject: Re: [phpGroupWare-developers] Nested db-objects
>
> ?This is not as Sigurd suggests a recent change. The change was
On Sat, 2008-05-24 at 16:23 +0200, Maât wrote:
> Sigurd Nes a écrit :
> > As Maât very elegantly wrote (he is my hero) - we need the freedom to do
> > studid things.
> >
>
> Please Sigurd, don't try to use my words for more than i intended to
> mean (sorry i'm going to loose the "hero" status
Sigurd Nes a écrit :
From: Maât [EMAIL PROTECTED]
Sent: 2008-05-24 16:23:04 CEST
To: phpgroupware-developers@gnu.org
Subject: Re: [phpGroupWare-developers] Nested db-objects
Sigurd Nes a écrit :
So - can I please have the nested db-objects?
If you ask me (but i'm just givi
> From: Maât [EMAIL PROTECTED]
> Sent: 2008-05-24 16:23:04 CEST
> To: phpgroupware-developers@gnu.org
> Subject: Re: [phpGroupWare-developers] Nested db-objects
>
> Sigurd Nes a écrit :
> > So - can I please have the nested db-objects?
> If you ask me (but i'm
Sigurd Nes a écrit :
As Maât very elegantly wrote (he is my hero) - we need the freedom to do studid
things.
Please Sigurd, don't try to use my words for more than i intended to
mean (sorry i'm going to loose the "hero" status)
I explained that framework should allow to do things... even
> From: Dave Hall [EMAIL PROTECTED]
> Sent: 2008-05-24 10:50:17 CEST
> To: phpgroupware-developers@gnu.org
> Subject: RE: [phpGroupWare-developers] Nested db-objects
>
> On Sat, 2008-05-24 at 10:40 +0200, Sigurd Nes wrote:
> > I will take all advice on code style serious
On Sat, 2008-05-24 at 10:40 +0200, Sigurd Nes wrote:
> As Maât very elegantly wrote (he is my hero) - we need the freedom to do
> studid things.
>
> I have been using my apps with success in production for years - and as we
> speek it is being implented at three hospitals and two municipals (8
As Maât very elegantly wrote (he is my hero) - we need the freedom to do studid
things.
I have been using my apps with success in production for years - and as we
speek it is being implented at three hospitals and two municipals (8 more are
in que).
And it is not good when it - BANG! - stop w
Dr. Christian Böttger a écrit :
We are not really far away from each other in the end in our opinions.
Here i globally agree :)
Regards,
Maât
___
phpGroupWare-developers mailing list
phpGroupWare-developers@gnu.org
http://lists.gnu.org/mailma
Maât schrieb:
I (very respectfully but very strongly) disagree... i explained already
twice why
not really because I was not able to invest enough time to explain all
the details. We are not really far away from each other in the end in
our opinions.
But again, I'm pressed to make it sho
Dr. Christian Böttger a écrit :
Well, it *has* to be "ready when ready" just like Debian. No body pays
us - it's all voluntary work. So how can anyone really impose any
deadline? Noone has a handle on the time people are able to commit to
the project.
Having said that: yes, we can agree on
Dr. Christian Böttger a écrit :
Hi,
Maât schrieb:
Rather than lock project evolution for religious reasons i think we
need to separate the tasks
standard procedures of software design like separation between
business logic and storage is NOT "religion". It's a standard method
for maintaina
Hi,
Sigurd Nes schrieb:
Why can't we do as Maât suggest - and we should all be happy:
write down quality rules or phpgroupware best practices to help app
developers create elegant code that will have a better effect on design
beauty and global performance and phpgw image than locking things
Hi,
I hate "AOL" posts, but this time I can only agree to Dave in this matter.
Dave Hall schrieb:
It was only done that way as it was the default PHP4 behaviour. PHP5
isn't PHP4. It was broken design back then and it is broken design now.
Things get fixed over time, and old hacks cease to w
Hi,
Olivier Berger schrieb:
Please make solid foundations (including test classes) so that things
like DB API are robust and tested ;)
I like some idea from extreme programming in this regard: first actually
write the test case (in software!) than do the coding in order to make
your module/
Hi,
Maât schrieb:
Rather than lock project evolution for religious reasons i think we need
to separate the tasks
standard procedures of software design like separation between business
logic and storage is NOT "religion". It's a standard method for
maintainable software development. It's no
Hi,
Sigurd Nes schrieb:
From: Dave Hall [EMAIL PROTECTED]
This isn't a tiny change. It is a major change.
I think its a tiny change to change it back
It's tiny in the number of characters to change but major in the
consequences.
The discussion about multiple database objects has
Hi,
Dave Hall schrieb:
In this case (connecting to an external system) you are working outside
the scope the db abstraction layer.
as you stated below (chopped out for redundancy cropping in answers...),
this is not a storage issue, but a business logic issue and has to be
handled in the
g
> >>> Subject: Re: [phpGroupWare-developers] Nested db-objects
> >>>
> >>> Le mercredi 21 mai 2008 à 20:02 +0200, Sigurd Nes a écrit :
> >>>> Hi all,
> >>>>
> >>>> I find it very useful to have the ability to have the c
Dave Hall wrote:
On Thu, 2008-05-22 at 15:06 +0200, Sigurd Nes wrote:
From: Olivier Berger [EMAIL PROTECTED]
Sent: 2008-05-22 13:35:48 CEST
To: phpgroupware-developers@gnu.org
Subject: Re: [phpGroupWare-developers] Nested db-objects
Le mercredi 21 mai 2008 à 20:02 +0200, Sigurd Nes a écrit
On Thu, 2008-05-22 at 15:06 +0200, Sigurd Nes wrote:
> > From: Olivier Berger [EMAIL PROTECTED]
> > Sent: 2008-05-22 13:35:48 CEST
> > To: phpgroupware-developers@gnu.org
> > Subject: Re: [phpGroupWare-developers] Nested db-objects
> >
> > Le mercredi 21 mai 20
> From: Olivier Berger [EMAIL PROTECTED]
> Sent: 2008-05-22 13:35:48 CEST
> To: phpgroupware-developers@gnu.org
> Subject: Re: [phpGroupWare-developers] Nested db-objects
>
> Le mercredi 21 mai 2008 à 20:02 +0200, Sigurd Nes a écrit :
> > Hi all,
> >
> > I fin
Le jeudi 22 mai 2008 à 21:49 +1000, Dave Hall a écrit :
> On Thu, 2008-05-22 at 13:35 +0200, Olivier Berger wrote:
>
> > Please make solid foundations (including test classes) so that things
> > like DB API are robust and tested ;)
>
> I have played with PHP Unit a fair bit recently, it is a grea
On Thu, 2008-05-22 at 13:35 +0200, Olivier Berger wrote:
> Please make solid foundations (including test classes) so that things
> like DB API are robust and tested ;)
I have played with PHP Unit a fair bit recently, it is a great tool. I
think it is too late to do much with it in 18, but for an
Le mercredi 21 mai 2008 à 20:02 +0200, Sigurd Nes a écrit :
> Hi all,
>
> I find it very useful to have the ability to have the choice of using nested
> db-objects.
>
> Example:
> When integrating with external systems - it is very convenient to start a
> transaction on system 1 - do some work
> From: Benoit Hamet [EMAIL PROTECTED]
> Sent: 2008-05-22 09:51:10 CEST
> To: phpgroupware-developers@gnu.org
> Subject: Re: [phpGroupWare-developers] Nested db-objects
>
> In my case, the db should be made singleton. That's clear.
Yep - that one was a very simple one
Sigurd Nes a écrit :
From: Dave Hall [EMAIL PROTECTED]
Except in the case of connecting to external systems, there should be no
need to clone the db object. If there is then your design is probably
broken.
Well - I respectfully disagree :)
Regards
Sigurd
I too respectfully dis
Hi all,
>>>
>>> I find it very useful to have the ability to have the choice of using
>>> nested
>>> db-objects.
>>>
>>> Example:
>>> When integrating with external systems - it is very convenient to start a
>>> transaction on system 1 - do some work (like sync) on system 2 - and if
>>> things
> From: Dave Hall [EMAIL PROTECTED]
> Sent: 2008-05-22 01:46:56 CEST
> To: phpgroupware-developers@gnu.org
> Subject: Re: [phpGroupWare-developers] Nested db-objects
>
> On Wed, 2008-05-21 at 20:02 +0200, Sigurd Nes wrote:
> > Hi all,
> >
> > I find it very us
On Wed, 2008-05-21 at 20:02 +0200, Sigurd Nes wrote:
> Hi all,
>
> I find it very useful to have the ability to have the choice of using nested
> db-objects.
>
> Example:
> When integrating with external systems - it is very convenient to start a
> transaction on system 1 - do some work (like s
Hi all,
I find it very useful to have the ability to have the choice of using nested
db-objects.
Example:
When integrating with external systems - it is very convenient to start a
transaction on system 1 - do some work (like sync) on system 2 - and if things
went well do a commit on the resu
33 matches
Mail list logo
