Hi Marcio, ah now I see.
I was already wondering what the XML Generation has to do with it, but yes, it uses getFunctionName() and sets it as an attribute on a column element. This might be a useful information e.g. when using XSLT to transform the XML, but the outcome is driver specific and it is questionalbe whether its benefit is worth the abstract function on DBFuncExpr(). To be honest I don't really have an option about this. I'd just leave it as it is - as long as it works and doesn't cause any exceptions. Regards Rainer Marcio Mazza wrote: > from: Marcio Mazza [mailto:[email protected]] > to: [email protected] > re: Re: AW: year "functionName" for Oracle > > Thanks for the answer, Rainer. > > Maybe I should clarify that the little test was just for > communication, and not to actually test functionality. > > The concern is that the method > String org.apache.empire.db.expr.column.DBFuncExpr.getFunctionName() > is used by > Element > org.apache.empire.db.expr.column.DBAbstractFuncExpr.addXml(Element > parent, long flags) > which is used by > boolean org.apache.empire.db.DBReader.addColumnDesc(Element > parent) > which is used by > Document org.apache.empire.db.DBReader.getXmlDocument() > > so maybe we may end up having something unexpected with the XML > generation. I really dunno. I'm still reading the codebase. > > By the way, I really think that the project should have more tests, > some of which would be integration tests, indeed. > > > > 2010/10/10 Andreas Fink <[email protected]>: > > oracle? never heard of ;-) > > > >> So since I am sure, that there are not many people using Oracle 8 or > an earlier version any more, I will change the default implementation > for the date extraction functions > > [...] > >> compatibility. > >> Does anyone have concerns about this? > > > > +1 for the change > > > > regards, > > andi > > > > > > -- > > web: http://andreasfink.com/ > > mail: �[email protected] > > mobil: +34 65 1728443 > > tel: +34 93 2082949 > > > >
