[daisy] regarding the DB2 issues -- @Aaron

[Aaron.Digulla at Globus.ch]

daisy-bounces at lists.cocoondev.org schrieb am 22.01.2007 12:12:30:

> >  You'll see these if you start 
> > to base your test cases in Derby, for example.
> > 
> > The issue about the length of the table names is probably DB2 specific 
but 
> > I hope that you can accept shorter names in your model :-)
> > 
> > When these are fixed, porting to new "big" DBs like Oracle and DB2 
(were 
> > JDBC support is nowhere as good as in MySQL :-( ) will be much more 
simple 
> > (namely writing or copying the Torque scripts).
> > 
> 
> Exactly. That's why I would very much welcome patches for *current
> trunk* that fix *specific issues*, i.e. a separate patch for the quote
> issue, a separate patch for the select null issue, etc. That way
> harmless enhancements can be easily committed.
> 
> Some items I really need to verify myself, like the DATE vs DATETIME
> thing (does that really give the exact same type in the mysql scripts as
> before?), before committing them, and that takes time.
> 
> And once more, your patch has never been committable to trunk because
> almost all SQL statements were touched as part of the introduction of
> namespaces. Now, let's stop talking about this ;-)

Unfortunately, I cannot submit patches against trunk because I have to use 
the current production version of Daisy. I'm not paid to support OSS, I'm 
paid to build production ready systems. Being the economy as it currently 
is, this is something we both can't do something about. So while your 
argument makes sense from an OSS point of view, it doesn't make sense from 
my point of view as a patch submitter.

My argument is this: It took me about thirty minutes to write these 
patches (the bigs ones are Search&Replace, the smaller ones are just a few 
lines where most of the time was spent finding the line).

I figure it will take *you* five minutes to look at the patch, understand 
what it fixes and port it to trunk. Therefore, your constant arguing 
against it is only achieving to infuriate me especially since it's a 
non-issue really. You've already spent more time arguing that it would 
take to fix the issue, goddamnit :-(

Okay, since it's now four months since I originally submitted the patches, 
it will take you more than five minutes because of all the changes you 
made since but that's something I can't change. I did all I could to 
prevent this from happening.

Regards,

-- 
Aaron Digulla